Systems, methods and apparatus to facilitate identification and acquisition of access points

ABSTRACT

Systems, apparatus and methods for facilitating identification and/or acquisition of an access point are provided. Methods can include transmitting or receiving access point information (“API”) indicative of an identification of the access point (“AP”). The API can be provided at the AP through hardwiring or receipt of configuration information input by a user or transmitted to the AP by a network operator through Over-The-Air (“OTA”) signaling. The API can be computer-readable and, in some embodiments, the API can also be human-readable. The API can be transmitted on a paging channel from which user equipment (“UE”) can receive information. The frequency at which the API is transmitted can be fixed, dynamic and/or configurable. Upon receipt of the API, acquisition of the AP is attempted if the AP is determined to be a permitted AP.

CLAIM OF PRIORITY UNDER 35 U.S.C. § 119

This application is a divisional application of U.S. application Ser.No. 13/538,495, entitled “Systems, Methods and Apparatus to FacilitateIdentification and Acquisition of Access Points,” filed Jun. 29, 2012,which is a divisional application of U.S. application Ser. No.12/501,807, entitled “Systems, Methods and Apparatus to FacilitateIdentification and Acquisition of Access Points,” filed Jul. 13, 2009and now issued as U.S. Pat. No. 8,229,440, which claimed priority toProvisional Application No. 61/080,618, entitled “Method and Apparatusto Provide a Femto Cell Identifier/Signalling Message for 1×RTT andWireless Systems,” filed Jul. 14, 2008, assigned to the assignee hereofand hereby expressly incorporated by reference herein.

BACKGROUND

Field

The present disclosure relates generally to wireless communications, andmore specifically, to systems, methods and apparatus for facilitatingidentification and/or acquisition of access points in wirelesscommunications systems.

Background

Wireless communication systems are widely deployed to provide varioustypes of communication (e.g., voice, data, multimedia services, etc.) tomultiple users. As the demand for high-rate and multimedia data servicesrapidly grows, there lies a challenge to implement efficient and robustcommunication systems with enhanced performance.

In recent years, users have started to replace fixed line communicationswith mobile communications and have increasingly demanded great voicequality, reliable service, and low prices.

In addition to mobile phone networks currently in place, a new class ofsmall access points has emerged, which can be installed in a user's homeand provide indoor wireless coverage to mobile units using existingbroadband Internet connections. Such access points are also known asminiature base stations, Home Node Bs (HNBs), or femto cells. Typically,such access points are connected to the Internet and the mobileoperator's network via DSL router or cable modem.

SUMMARY

The following presents a simplified summary of one or more aspects inorder to provide a basic understanding of such aspects. This summary isnot an extensive overview of all contemplated aspects, and is intendedto neither identify key or critical elements of all aspects nordelineate the scope of any or all aspects. Its sole purpose is topresent some concepts of one or more aspects in a simplified form as aprelude to the more detailed description that is presented later.

According to an aspect, a method for facilitating identification andacquisition of an access point is provided. The method can include:receiving access point information indicative of an identification ofthe access point; and in response to determining that the access pointis a permitted access point, attempting acquisition of the access point.

According to another aspect, a computer program product is provided. Thecomputer program product can include a computer-readable medium. Thecomputer-readable medium can include: code for causing at least onecomputer to receive access point information indicative of anidentification of an access point; and code for causing at least onecomputer to attempt acquisition of the access point in response todetermining that the access point is a permitted access point.

According to another aspect, an apparatus is provided. The apparatus caninclude: means for receiving access point information indicative of anidentification of an access point; means for masking a portion of theaccess point information; means for comparing an unmasked portion of theaccess point information with information indicative of identities ofone or more access points to which access by the apparatus isauthorized; and means for attempting to acquire the access point if themeans for comparing generates an output indicative of the apparatusbeing permitted to access the access point.

According to another aspect, another apparatus is provided. Theapparatus can include: a user equipment (“UE”) database moduleconfigured to store information indicative of identities of one or moreaccess points to which access by the apparatus is authorized; a UEreceiver module configured to receive a first signal including accesspoint information indicative of an identification of an access pointproximate to a geographical location of the apparatus; a UE filtermodule coupled to the UE receiver module and configured to mask aportion of the received access point information; a UE processor modulecoupled to the UE filter module and the UE database module andconfigured to compare an unmasked portion of the access pointinformation with the information indicative of identities of one or moreaccess points to which access by the apparatus is authorized, anddetermine whether the access point is a permitted access point based ona result of the comparison; and a UE transmitter module coupled to theUE processor module and configured to transmit a signal to the accesspoint for attempting acquisition of the access point if the UE processormodule determines that the access point is a permitted access point.

According to another aspect, a method is provided. The method caninclude: transmitting, to user equipment, access point informationindicative of an identification of the access point; receiving, from theuser equipment, information indicative of a registration request,wherein the registration request is transmitted by the user equipment ifthe user equipment determines that the access point is a permittedaccess point; and providing access to the user equipment in response toreceiving the information indicative of the registration request.

According to another aspect, a computer program product having acomputer-readable medium is provided. The computer-readable medium caninclude: code for causing at least one computer to transmit to userequipment access point information indicative of an identification ofthe access point; code for causing at least one computer to receiveinformation indicative of a registration request from the user equipmentin response to transmitting the access point information if the userequipment determines that that the access point is a permitted accesspoint; and code for causing at least one computer to provide access tothe user equipment in response to receiving the information indicativeof the registration request.

According to another aspect, an apparatus is provided. The apparatus caninclude: means for transmitting to user equipment, access pointinformation indicative of an identification of the access point; meansfor receiving information indicative of a registration request from theuser equipment in response to transmitting the access point information;and means for permitting the user equipment to access the apparatus ifthe user equipment is permitted to access the apparatus.

According to another aspect, an apparatus is provided. The apparatus caninclude: a database module configured to store information indicative ofone or more user equipment authorized to access the apparatus; a memorymodule configured to store first access point information indicative ofthe identity of the apparatus; a transmitter module configured totransmit the first access point information; a receiver moduleconfigured to receive a first signal including information indicative ofa registration request from the user equipment; and a processor moduleconfigured to provide access to the user equipment if the user equipmentis authorized to access the apparatus.

According to another aspect, a method is provided. The method caninclude: transmitting, by user equipment, handoff information receivedfrom the target access point. The handoff information can include:information indicative of an identity of a mobile switching center towhich the target access point is associated; and information indicativeof an identity of a cell to which the target access point is associated.

According to another embodiment, a computer program product having acomputer-readable medium is provided. The computer-readable medium caninclude: code for causing a computer to receive transmitted handoffinformation from a target access point. The handoff information caninclude: information indicative of an identity of a mobile switchingcenter to which the target access point is associated; and informationindicative of an identity of a cell to which the target access point isassociated.

According to another aspect, an apparatus is provided. The apparatus caninclude: a receiver module configured to receive transmitted handoffinformation from a target access point. The handoff information caninclude: information indicative of an identity of a mobile switchingcenter to which the target access point is associated; and informationindicative of an identity of a cell to which the target access point isassociated. The apparatus can also include: a memory module configuredto store the handoff information; and a processor module configured toprocess the handoff information and control a transmitter module totransmit the handoff information to initiate handoff to the targetaccess point.

According to another aspect, an apparatus is provided. The apparatus caninclude: means for receiving transmitted handoff information from atarget access point. The handoff information can include: informationindicative of an identity of a mobile switching center to which thetarget access point is associated; and information indicative of anidentity of a cell to which the target access point is associated. Theapparatus can also include: means for storing the handoff information;means for transmitting the handoff information; and means for processingthe handoff information and controlling the means for transmitting totransmit the handoff information to initiate handoff to the targetaccess point.

According to another aspect, a method is provided. The method includes:facilitating identification and acquisition of a femto cell accesspoint, the method comprising: transmitting, to user equipment, accesspoint information indicative of an identification of the femto cellaccess point.

According to another aspect, a method is provided. The method can be amethod for performing handoff of a mobile station (“MS”) from a macrobase station controller (“Macro BS”) of a macro cell to a target femtoaccess point (“target femto AP”). The method can include: transmitting,by the MS to the macro cell, information indicative of signal strengthinformation, wherein the signal strength information includes a pilotstrength measurement; determining, by the Macro BS, whether to performhandoff of the MS to the target femto AP; and, in response todetermining that handoff should be performed, signaling to a mobileswitching center (“MSC”), a message for requesting handoff. The methodcan also include: determining, by the MSC, that a target cell isassociated with information indicative of an identity of the MSC for afemto convergence server (“FCS”), and transmitting a facilitiesdirective message to the FCS associated with the target cell. The methodcan also include: reserving, by the FCS, an inter-vendor trunk (“IVT”)port for terminating the IVT identified with the facilities directivemessage, and media gateway (“MGW”) resources to terminate a real-timetransport protocol (“RTP”) bearer path with the target femto AP. Themethod can also include: transmitting, by the FCS to one or morecandidate femto access points (“femto APs”), a session initiationprotocol (“SIP”) message with a measurement request for the MS if nofemto AP can be uniquely determined as the target femto AP. The methodcan also include: attempting to detect, by the one or more candidatefemto APs, the MS and measure the signal strength of an MS uplink whilethe MS is engaged in an active voice call over a network provided in themacro cell; and transmitting, by the one or more candidate femto APs tothe FCS, the measured signal strengths, wherein transmitting to the FCSincludes transmitting the measured signal strengths to a call sessioncontrol function (“CSCF”), and the CSCF transmitting the measured signalstrengths to the FCS. The method can also include: determining, by theFCS, as the target femto AP to which handoff should be performed, one ofthe one or more candidate femto APs, based on the measured signalstrengths received at the FCS; and transmitting, by the FCS to thetarget femto AP, a SIP invite message, the SIP invite message beingindicative of a handoff request. The method can also include:transmitting, by the target femto AP, information indicative ofacknowledgement of the handoff request; establishing a voice/bearer pathfor the MS; and transmitting, by the FCS, to the MSC, a MobileApplication Part (“MAP”) facilities directive return result messageconfirming establishment of an IVT connection. The method can alsoinclude: transmitting, by the MSC and via the Macro BS, informationdirecting the MS to handoff to the target femto AP; transmitting, fromthe MS to the target femto AP, a handoff complete message; acquiring aforward link traffic channel from the target femto AP; and establishinga voice path between the MS and the target femto AP.

To the accomplishment of the foregoing and related ends, the one or moreaspects comprise the features hereinafter fully described andparticularly pointed out in the claims. The following description andthe annexed drawings set forth in detail certain illustrative featuresof the one or more aspects. These features are indicative, however, ofbut a few of the various ways in which the principles of various aspectsmay be employed, and this description is intended to include all suchaspects and their equivalents.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an exemplary wireless communication system foridentification and/or acquisition of access points according to anembodiment;

FIG. 2A illustrates an exemplary communication system where one or morefemto access points are deployed within a network environment accordingto an embodiment;

FIG. 2B illustrates an example of a coverage map where several trackingareas (or routing areas or location areas) are defined, each of whichincludes several macro coverage areas according to an embodiment;

FIG. 3 illustrates an exemplary block diagram of an access pointaccording to an embodiment;

FIG. 4A illustrates another exemplary block diagram of an access pointaccording to an embodiment;

FIG. 4B illustrates another exemplary block diagram of an access pointaccording to an embodiment;

FIG. 5 illustrates an exemplary flowchart of a method for facilitatingidentification and/or acquisition of an access point according to anembodiment;

FIG. 6 illustrates an exemplary block diagram of user equipmentaccording to an embodiment;

FIG. 7A illustrates another exemplary block diagram of user equipmentaccording to an embodiment;

FIG. 7B illustrates another exemplary block diagram of an access pointaccording to an embodiment;

FIG. 8 illustrates an exemplary flowchart of a method for facilitatingacquisition of an access point according to an embodiment;

FIG. 9A illustrates an exemplary embodiment of a call flow diagram ofhandoff of user equipment from a macro cell to an access point accordingto an embodiment;

FIG. 9B illustrates an exemplary embodiment of a call flow diagram ofhandoff of user equipment from an access point to a macro cell accordingto an embodiment;

FIG. 9C illustrates an exemplary block diagram of a system forperforming handoff from a macro cell to a femto access point accordingto an embodiment;

FIG. 10A illustrates a first partial view of an exemplary embodiment ofa call flow diagram of handoff of a mobile station from a Macro basestation controller to a femto access point according to an embodiment;

FIG. 10B illustrates a second partial view of an exemplary embodiment ofa call flow diagram of handoff of a mobile station from a Macro basestation controller to a femto access point according to an embodiment;

FIG. 10C illustrates a first partial view of an exemplary embodiment ofa call flow diagram of handoff of a mobile station from a femto accesspoint to a macro base station controller according to an embodiment;

FIG. 10D illustrates a second partial view of an exemplary embodiment ofa call flow diagram of handoff of a mobile station from a femto accesspoint to a macro base station controller according to an embodiment; and

FIG. 11 illustrates exemplary components that may be employed tofacilitate communication between nodes.

DETAILED DESCRIPTION

Various aspects are now described with reference to the drawings. In thefollowing description, for purposes of explanation, numerous specificdetails are set forth in order to provide a thorough understanding ofone or more aspects. It may be evident, however, that such aspect(s) maybe practiced without these specific details.

As used in this patent application, the terms “component,” “module,”“system” and the like are intended to include a computer-related entity,such as but not limited to hardware, firmware, a combination of hardwareand software, software, or software in execution. For example, acomponent can be, but is not limited to being, a process running on aprocessor, a processor, an object, an executable, a thread of execution,a program, and/or a computer. By way of illustration, both anapplication running on a computing device and the computing device canbe a component. One or more components can reside within a processand/or thread of execution and a component may be localized on onecomputer and/or distributed between two or more computers. In addition,these components can execute from various computer readable media havingvarious data structures stored thereon. The components may communicateby way of local and/or remote processes such as in accordance with asignal having one or more data packets, such as data from one componentinteracting with another component in a local system, distributedsystem, and/or across a network such as the Internet with other systemsby way of the signal.

Furthermore, various aspects are described herein in connection with aterminal, which can be a wired terminal or a wireless terminal. Aterminal can also be called a system, device, subscriber unit,subscriber station, mobile station, mobile, mobile device, remotestation, remote terminal, access terminal, user terminal, communicationdevice, user agent, user device, or user equipment (“UE”). A wirelessterminal can be a cellular telephone, a satellite phone, a cordlesstelephone, a Session Initiation Protocol (“SIP”) phone, a wireless localloop (“WLL”) station, a personal digital assistant (“PDA”), a handhelddevice having wireless connection capability, a computing device, and/orother processing devices connected to a wireless modem. Moreover,various aspects are described herein in connection with an access pointand/or base station. An access point can be utilized for communicatingwith wireless terminal(s) and can also be referred to as a Node B, anaccess node, base station and/or some other terminology. Further, it isunderstood that while the terms “access point,” “AP” and/or “femto AP”may be used herein, the embodiments described herein may also beemployed in cells of other types or geographical scopes including, butnot limited to, personal cells generally limited to the body of a userand/or pico cells. A base station can be used for communicating with aterminal and/or an AP. It is understood that the base station can alsobe referred to as the macro network.

Moreover, the term “or” is intended to mean an inclusive “or” ratherthan an exclusive “or.” That is, unless specified otherwise, or clearfrom the context, the phrase “X employs A or B” is intended to mean anyof the natural inclusive permutations. That is, the phrase “X employs Aor B” is satisfied by any of the following instances: X employs A; Xemploys B; or X employs both A and B. In addition, the articles “a” and“an” as used in this application and the appended claims shouldgenerally be construed to mean “one or more” unless specified otherwiseor clear from the context to be directed to a singular form.

The techniques described herein may be used for various wirelesscommunication systems such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA and othersystems. The terms “system” and “network” are often usedinterchangeably. A CDMA system may implement radio technologies such asUniversal Terrestrial Radio Access (UTRA), cdma2000, cdma2000 1×RTT,etc. UTRA includes Wideband-CDMA (W-CDMA) and other variants of CDMA.Further, cdma2000 covers IS-2000, IS-95 and IS-856 standards. High DataRate Packet Data (“HRPD”) radio technologies, including, but not limitedto, cdma2000 1×EV-DO, can also be implemented. A TDMA system mayimplement a radio technology such as Global System for MobileCommunications (GSM). An OFDMA system may implement a radio technologysuch as Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11(Wi-Fi), IEEE 802.15 (WiMAX), IEEE 802.20, Flash-OFDM, etc. UTRA andE-UTRA are part of Universal Mobile Telecommunication System (UMTS).3GPP Long Term Evolution (LTE) is a release of UMTS that uses E-UTRA,which employs OFDMA on the downlink and SC-FDMA on the uplink. UTRA,E-UTRA, UMTS, LTE and GSM are described in documents from anorganization named “3rd Generation Partnership Project” (3GPP).Additionally, cdma2000 and UMB are described in documents from anorganization named “3rd Generation Partnership Project 2” (3GPP2).Further, such wireless communication systems may additionally includepeer-to-peer (e.g., mobile-to-mobile) ad hoc network systems often usingunpaired unlicensed spectrums, 802.xx wireless LAN, BLUETOOTH and anyother short- or long-range, wireless communication techniques.

Various aspects or features will be presented in terms of systems thatmay include a number of devices, components, modules, and the like. Itis to be understood and appreciated that the various systems may includeadditional devices, components, modules, etc. and/or may not include allof the devices, components, modules etc. discussed in connection withthe figures. A combination of these approaches may also be used.

FIG. 1 illustrates an exemplary wireless communication system foridentification and/or acquisition of access points according to anembodiment. The system 100 provides communication for multiple cells112, such as, for example, macro cells 112A-112G, with each cell beingserviced by a corresponding access node (“AN”) 114 (e.g., access nodes114A-114G). As shown in FIG. 1, UEs 116 (e.g., UEs 116A-116L) may bedispersed at various locations throughout the system over time. Each UE116 may communicate with one or more access nodes 114 on a forward link(“FL”) and/or a reverse link (“RL) at a given moment, depending uponwhether the UE 116 is active and whether it is in soft handoff, forexample. The wireless communication system 110 may provide service overa large geographic region. For example, macro cells 112A-112G may covera few blocks in a neighborhood.

In some aspects the teachings herein may be employed in a network thatincludes macro scale coverage (e.g., a large area cellular network suchas a 3G networks, typically referred to as a macro cell network) andsmaller scale coverage (e.g., a residence-based or building-basednetwork environment). As a UE moves through such a network, the UE maybe served in certain locations by access nodes that provide macrocoverage while the UE may be served at other locations by access nodesthat provide smaller scale coverage. In some aspects, the smallercoverage nodes may be used to provide incremental capacity growth,in-building coverage, and different services (e.g., for a more robustuser experience). In the discussion herein, a node that providescoverage over a relatively large area may be referred to as a macronode. A node that provides coverage over a relatively small area (e.g.,a residence) may be referred to as a femto AP. A node that providescoverage over an area that is smaller than a macro area and larger thana femto area may be referred to as a pico node (e.g., providing coveragewithin a commercial building).

A cell associated with a macro node, a femto AP, or a pico node may bereferred to as a macro cell, a femto cell, or a pico cell, respectively.In some implementations, each cell may be further associated with (e.g.,divided into) one or more sectors.

In various applications, other terminology may be used to reference amacro node, a femto AP, or a pico node. For example, a macro node may beconfigured or referred to as an access node, base station, access point,node, eNodeB, macro cell, and so on. Also, a femto AP may be configuredor referred to as a Home NodeB, Home eNodeB, access point base station,femto cell, and so on.

FIG. 2A illustrates an exemplary communication system where one or morefemto access points are deployed within a network environment.Specifically, the system 200 includes multiple femto APs 210 (e.g.,femto APs 210 and 212) installed in a relatively small scale networkenvironment (e.g., in one or more user residences 214). Each femto AP210 may be coupled to a wide area network 240 (e.g., the Internet) and amobile operator core network 250 via a DSL router, a cable modem, awireless link, or other connectivity means (not shown). A mobileswitching center (not shown) can also be communicatively coupled to theAPs 210, 212 for facilitating handoff between or with APs generally,facilitating Over-The-Air (“OTA”) configuration services for APs 210,212, and/or facilitating communications between the UE 220 and terminalscommunicating over a circuit-switched network. As will be discussedbelow, each femto AP 210 may be configured to serve associated UEs 220(e.g., UE 220A) and, optionally, alien UEs 220 (e.g., UE 220B). In otherwords, access to femto APs 210 may be restricted whereby a given UE 220may be served by a set of designated (e.g., home) femto APs 210 but maynot be served by any non-designated femto APs (e.g., a neighbor's femtoAP) (not shown).

For simplicity of notation, the description will continue using thenotation indicative of a single femto AP, i.e., “femto AP 210.” However,it is to be understood that the term “femto AP 210” can refer tomultiple femto APs, such as APs 210, 212, as appropriate given thedescription. Additionally, although embodiments described herein use3GPP terminology, it is to be understood that the embodiments can beapplied to 3GPP (Rel99, Rel5, Rel6, Rel7, Rel8) technology, as well as3GPP2 (1×RTT, 1×EV-DO Rel0, RevA, RevB) technology and other known andrelated technologies.

FIG. 2B illustrates an example of a coverage map 270 where severaltracking areas 272 (or routing areas or location areas) are defined,each of which includes several macro coverage areas 274. Here, areas ofcoverage associated with tracking areas 272A, 272B, and 272C aredelineated by the wide lines and the macro coverage areas 274 (e.g.,274A, 274B, 274C) are represented by the hexagons. The tracking areas272 also include femto coverage areas 276 (e.g., 276A, 276B, 276C,276D). In this example, each of the femto coverage areas 276 (e.g.,femto coverage area 276C) is depicted within a macro coverage area 274(e.g., macro coverage area 274B). It should be appreciated, however,that a femto coverage area 276 may not lie entirely within a macrocoverage area 274. In practice, a large number of femto coverage areas276 may be defined with a given tracking area 272 or macro coverage area274. Also, one or more pico coverage areas (not shown) may be definedwithin a given tracking area 272 or macro coverage area 274.

Referring again to FIG. 2A, the owner of a femto AP 210 may subscribe tomobile service, such as, for example, 3G mobile service, offered throughthe mobile operator core network 250. In addition, a UE 220 may becapable of operating both in macro environments and in smaller scale(e.g., residential) network environments. In other words, depending onthe current location of the UE 220, the UE 220 may be served by anaccess node 260 of the macro cell mobile network 250 or by any one of aset of femto APs 210 (e.g., the femto APs 210 and 212 that reside withina corresponding user residence 214). For example, when a subscriber isoutside his home, he is served by a standard macro access node (e.g.,node 260) and when the subscriber is at home, he is served by a femto AP(e.g., node 210). Here, it should be appreciated that a femto AP 220 maybe backward compatible with existing UEs 220.

A femto AP 210 may be deployed on a single frequency or, in thealternative, on multiple frequencies. Depending on the particularconfiguration, the single frequency or one or more of the multiplefrequencies may overlap with one or more frequencies used by a macronode (e.g., node 260).

In some aspects, a UE 220 may be configured to connect to a preferredfemto AP (e.g., the home femto AP 210 of the UE 220) whenever suchconnectivity is possible. For example, whenever the UE 220 is within theuser's residence 214, it may be desired that the UE 220 communicate onlywith the home femto AP 210.

In some aspects, if the UE 220 operates within the macro cellularnetwork 250 but is not residing on its most preferred network (e.g., asdefined in a preferred roaming list), the UE 220 may continue to searchfor the most preferred network (e.g., the preferred femto AP 210) usinga Better System Reselection (“BSR”), which may involve a periodicscanning of available systems to determine whether better systems arecurrently available, and subsequent efforts to associate with suchpreferred systems. With the acquisition entry, the UE 220 may limit thesearch for specific band and channel. For example, the search for themost preferred system may be repeated periodically. Upon discovery of apreferred femto AP 210, the UE 220 selects the femto AP 210 for campingwithin its coverage area.

A femto AP may be restricted in some aspects. For example, a given femtoAP may only provide certain services to certain UEs. In deployments withso-called restricted (or closed) association, a given UE may only beserved by the macro cell mobile network and a defined set of femto APs(e.g., the femto APs 210 that reside within the corresponding userresidence 214). In some implementations, a node may be restricted to notprovide, for at least one node, at least one of: signaling, data access,registration, paging, or service.

In some aspects, a restricted femto AP (which may also be referred to asa Closed Subscriber Group Home NodeB) is one that provides service to arestricted provisioned set of UEs. This set may be temporarily orpermanently extended as necessary. In some aspects, a Closed SubscriberGroup (“CSG”) may be defined as the set of access nodes (e.g., femtoAPs) that share a common access control list of UEs. A channel on whichall femto APs (or all restricted femto APs) in a region operate may bereferred to as a femto channel.

Various relationships may thus exist between a given femto AP and agiven UE. For example, from the perspective of a UE, an open femto APmay refer to a femto AP with no restricted association. A restrictedfemto AP may refer to a femto AP that is restricted in some manner(e.g., restricted for association and/or registration). A home femto APmay refer to a femto AP on which the UE is authorized to access andoperate on. A guest femto AP may refer to a femto AP on which a UE istemporarily authorized to access or operate on. An alien femto AP mayrefer to a femto AP on which the UE is not authorized to access oroperate on, except for perhaps emergency situations (e.g., 911 calls).

From a restricted femto AP perspective, a home UE may refer to a UE thatauthorized to access the restricted femto AP. A guest UE may refer to aUE with temporary access to the restricted femto AP. An alien UE mayrefer to a UE that does not have permission to access the restrictedfemto AP, except for perhaps emergency situations, for example, such as911 calls (e.g., a UE that does not have the credentials or permissionto register with the restricted femto AP).

For convenience, the disclosure herein describes various functionalityin the context of a femto AP. It should be appreciated, however, that apico node may provide the same or similar functionality for a largercoverage area. For example, a pico node may be restricted, a home piconode may be defined for a given UE, and so on.

A wireless multiple-access communication system may simultaneouslysupport communication for multiple wireless UEs. As mentioned above,each terminal may communicate with one or more base stations viatransmissions on the forward and reverse links. The forward link (ordownlink) refers to the communication link from the base stations to theterminals, and the reverse link (or uplink) refers to the communicationlink from the terminals to the base stations. This communication linkmay be established via a single-in-single-out system, amultiple-in-multiple-out (“MIMO”) system, or some other type of system.

A MIMO system employs multiple (N_(T)) transmit antennas and multiple(N_(R)) receive antennas for data transmission. A MIMO channel formed bythe N_(T) transmit and N_(R) receive antennas may be decomposed intoN_(S) independent channels, which are also referred to as spatialchannels, where N_(S)≤min{N_(T), N_(R)}. Each of the N_(S) independentchannels corresponds to a dimension. The MIMO system may provideimproved performance (e.g., higher throughput and/or greaterreliability) if the additional dimensionalities created by the multipletransmit and receive antennas are utilized.

A MIMO system may support time division duplex (“TDD”) and frequencydivision duplex (“FDD”). In a TDD system, the forward and reverse linktransmissions are on the same frequency region so that the reciprocityprinciple allows the estimation of the forward link channel from thereverse link channel. This enables the access point to extract transmitbeam-forming gain on the forward link when multiple antennas areavailable at the access point.

FIG. 3 illustrates an exemplary block diagram of an access pointaccording to an embodiment. Referring to FIGS. 2A and 3, a descriptionof an exemplary AP 210 will now be described. The AP 210 can include adatabase module 310, a transmitter module 320, a receiver module 330, aprocessor module 340 and a memory module 350. The database module 310can be communicatively coupled to the processor module 340, which can becommunicatively coupled to the memory module 350. The processor module340 can be communicatively coupled to the receiver module 330 and thetransmitter module 320.

In one or more embodiments, the AP 210 is configured to facilitateidentification and/or acquisition of the AP 210 by UEs 220 to which theAP 210 permits access. Similarly, the AP 210 can be configured toprevent acquisition of the AP 210 by UEs 220 to which the AP 210 has notpermitted access. If the UE 220 is not permitted to access the AP 210,the UE 220 may optionally continue an ongoing call, or initiate a newcall, with another nearby AP or a cellular network. As used herein, theterms “acquire” and “acquisition,” can include, but are not limited to,authentication and/or registration with the AP. By way of example, butnot limitation, attempting acquisition of an AP can include attemptingauthentication to the AP.

The memory module 350 can include any number of different types ofmemory for facilitating identification and/or acquisition of an AP 210.By way of example, but not limitation, the memory module 350 can be aread-only memory, a read-write memory and/or a memory card storing oneor more different types of information about the AP 210 including, butnot limited to, access point information (“API”) indicative of anidentifier of the AP 210. The API can be included in a message foridentifying the AP 210 to the UE 220 (“APIDM”).

The API can be of one or more different forms of information and/orlengths. For example, in one embodiment, the API can be acomputer-readable address, including, but not limited to an IP address.The IP address could be an IPv6 address, for example. In someembodiments, the API need not be an IP address or an IPv6 address. Insome embodiments, the API can be any information (or any portion ofinformation) capable of identifying the AP 210. In some embodiments, theAPI can be any computer-readable information capable of being read by acomputer and/or processor to identify the AP 210.

In some embodiments, the API can be a human-readable address such as ahuman-readable text string. For example, a 32 bit text string could beused. The text string could be readable by an owner of the UE 200 towhich the API is transmitted could be used. As such, the owner of a UE220 receiving the API can use the human-readable address to easilyidentify the AP 210, manually select between one or more AP with easeand/or manage one or more lists of APs to which the UE 220 is permittedto access (e.g., a white list) or to which the UE 220 is not permittedto access (e.g., a black list).

In some embodiments, the text string can be any number of bytes enablinga human operator of the UE 220 to discern the text string given theconstraints on the screen of the UE 220 and usage models of the UE 220.In one embodiment, the text string can be 32 bytes, as with the WiFinetwork name (“WiFi SSID”).

In some embodiments, the human-readable address can be a civic addresssuch as that defined in the Internet Engineering Task Force RFC 4776,“Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option forCivic Address Configuration Information,” November 2006. The address cansupport provisioning of a human-readable address in different languagesand/or in a format very similar to that used by postal deliveryservices. The civic address can be 255 octet address in someembodiments.

In some embodiments, the API can include the computer-readable addressas well as the human-readable address. As such, in some embodiments, afirst API can have a first length and a second API could have a secondlength. As such, in some embodiments, two or more APIs, of differinglengths and/or differing types of information, could be selectively usedby the API based on the need to reduce traffic on the channel on whichthe API is transmitted, based on the preferences for ease of human usewith which the AP 210 might be configured, or otherwise.

In some embodiments, the API can be any length. In some embodiments, theAPI can be any length allowing a substantial number of APs 210 to haveunique APIs without reuse within a system. In some embodiments, the APIcan be 48 bits long or 128 bits long. In some embodiments, the API canbe combined with information indicative of the system with which the AP210 is associated (“SID”) to generate a globally unique identifier. Asdescribed herein, when the API is described, such could include the APIwith or without the SID (and therefore the API in isolation or theglobally unique identifier, respectively).

In various embodiments, the API can be configured by a user of the AP210, a user of a UE 220 associated with the AP 210 and/or by a networkoperator from a location remote from the AP associated with the API. Byway of example, but not limitation, the network operator could provideinformation for configuring the API through Over-The-Air (“OTA”)signaling. Still, in some embodiments, the API can be hardwired orotherwise associated with or stored in the AP 210 at or prior to thetime of purchase of the AP 210. Yet still, in various embodiments, theAPI for a selected AP 210 could be configurable, fixed or dynamic. Forexample, the API could change over time. The factors determining whetherand when the API changes could include, but are not limited to, theamount of time that the API has been the same, the arrival of new APs210 in close proximity to the AP 210, user choice and/or user or networkoperator selection of a new or previously-used API or the like.

The memory module 350 can also store information about the AP 210 (thatcan also be provided in the APIDM) indicative of a frequency on whichthe AP 210 provides communication, band classes and/or channelbandwidths according to which the AP 210 can provide communicationservices to the UE 220. As such, a UE 220 permitted to access the AP 210can learn of the identity of the AP 210, acquire the AP 210 and tune thereceiver of the UE 220 to receive communications on the frequencyassociated with the AP 210.

In other embodiments, the memory module 350 can store, in addition tothe API, information indicative of a mobile switching center (“MSC_ID”)and/or the geographical (e.g., physical) location or area of the cellthat the AP 210 covers (“Cell_ID”). As such, the MSC_ID and the Cell_IDcan be provided in the APIDM and accessed by the UE 220 to facilitatehandoff from the AP 210 to another AP. In some embodiments, the MSC_IDand the Cell_ID can be analogous in size and placement within the APIDMto that shown for the size and placement of the IOS_MSC_ID and theIOS_Cell_ID within the APIDM as disclosed in Upper Layer (Layer 3)Signaling Standard for cdma2000 Spread Spectrum Systems, Release E,3GPP2 C.S0005-E, section 3.7.2.3.2.39, Access Point IdentificationMessage, v. 0.3, May 2009. As detailed in the above-referenced standard,the IOS_MSC_ID and the IOS_Cell_ID can be assigned respective values foruse by other APs (or network base stations or controllers) forperforming handoff with the AP 210.

In other embodiments, the memory module 350 can store, in addition to orin lieu of the API and/or the MSC_ID and/or the Cell_ID, informationindicative of the latitude, longitude and/or the altitude of the AP 210.The information indicative of the altitude can be provided to the UE 220for position location services, providing vertical distinction of APsthat are co-located horizontally, and/or for enabling a UE 220 to obtainheight information. Further, information indicative of partial almanacmacro cell base station information can be tailored for the region ofthe AP 210 and provided to indicate to the UE 220, the globalpositioning system (“GPS”) location of the pilots of neighboring APs.Further, information indicative of the SID and/or the identification ofthe network or base station with which the AP 210 or other APs areassociated (i.e., “Base_ID” or “NID”) can be stored in the AP 210.

The memory module 350 information can be stored in the memory prior toor at the time of purchase and/or stored upon receipt of configurationinformation through OTA signaling. With reference to FIGS. 2A and 3, forexample, the memory module 350 can store information received from themobile operator core network 250 (e.g., Sprint, Nextel) through OTAsignaling to/from the mobile operator core network 250. By way ofexample, but not limitation, the information through OTA signaling canbe for configuring, providing or changing the API for the AP (in casesin which the AP 210 was not hardwired or otherwise pre-configured withthe API prior to or at the time of purchase of the AP), the frequencywith which the API should be broadcast using a beacon signal of the API,and/or any other operational features of the AP 210. For example, in oneembodiment, the mobile operator core network 250 can provide OTAsignaling to configure the AP with a selected API, for broadcasting theAPI on a paging channel to which the UE 220 can receive communications,to transmit the communication at a slot cycle index (“SCI”) of 0 (i.e.,approximately every 1.28 seconds) or at a slot cycle index of 1 (i.e.,approximately every 2.56 seconds).

The database module 310 can be communicatively coupled to the memorymodule 350 and can store one or more different types of information forfacilitation of identification and/or acquisition of the AP 210 and/orfor handoff to or from other APs. For example, the database module 310can store information indicative of the identity of one or more UEs 220permitted (or not permitted) to acquire the AP 210. As another example,the database module 310 can store the information indicative of terms ofaccess for the one or more UEs 220 may be permitted to access the AP210. For example, terms of access can be accessed by the AP 210 indetermining whether to allow access based on the time of access, thefrequency of access or otherwise.

As another example, the database module 310 can store informationindicative of one or more other neighboring APs in geographic proximityto the AP 210. The information can be included as part of a neighborlist. The information indicative of the neighboring APs can include, butis not necessarily limited to, the identities, communicationfrequencies, band classes and/or channel bandwidths of the neighboringAPs. The information can be retrieved from the memory module 350 andbroadcast by the AP 210 in a neighbor list message (“NLM”). In someembodiments, the information that would typically be provided in an NLMis stored in a database associated with the UE 220 and the AP 210 neednot broadcast the NLM.

In some embodiments, the information stored in the database module 310indicative of the neighboring APs in geographic proximity to the AP 210can be enhanced to also include global positioning system (“GPS”)information indicative of GPS coordinates of the neighboring APs. Theenhanced information can be retrieved from the memory module 350 andbroadcast by the AP 210 in an enhanced general neighbor list message(“GNLM”) for providing the GPS location of neighboring APs to the UE220.

In various embodiments, the information stored in the database module310 and provided in the GNLM can be used by the UE 220 to select an APlisted in the GNLM based on a prioritization of available APs asdictated by the preferred user zone list (“PUZL”) priority scheme anddatabase that can be configured in the UE 220 as defined in“Over-the-Air Service Provisioning of Mobile Stations in Spread SpectrumSystems,” published as TIA-683-C, March 2003, which is incorporatedherein by reference. The GNLM can therefore allow the use of the PUZLentries in the database module of the UE 220 for specifying a smallerradius of acceptable APs from which the UE 220 can select for potentialacquisition. The GNLM can also be used to restrict the geographicalregion over which the UE 220 scans for APs.

In various embodiments, the database module 310 can be providedinformation through configuration via a memory card, temporary orpermanent manual or other programming of the database module prior to orat the time of purchase of the AP 210 and/or OTA signaling from a mobileoperator core network 250.

The transmitter module 320 and the receiver module 330 can becommunicatively coupled to the processor. The transmitter module 320 canbe configured to broadcast within the geographical area covered by theAP 210, the API.

The transmitter module 320 could be configured to be controlled by theprocessor module 340 to broadcast the API based on the type or length ofthe API. For example, the transmitter module 320 of the AP 210 couldbroadcast a first API having a first length at a first frequency and asecond API having a second length at a second frequency. If the lengthof the first API is longer than the length of the second API (e.g., ifthe first API includes the computer-readable address and thehuman-readable address while the second API includes only thecomputer-readable address), the frequency at which the first API isbroadcast could be less than the frequency at which the second API isbroadcast.

Further, the transmitter module 320 could be configured to broadcast anyAPI on a selected channel and occurring selected frequency. By way ofexample, but not limitation, the API could be broadcast on a pagingchannel to which the UE 220 is configured to listen. In someembodiments, the API can be transmitted in an existing message on thepaging channel (e.g., a System Parameter Message on the paging channelfor cdma2000 1×RTT or a Sector Parameter Message on the paging channelfor cdma2000 1×EV-DO).

For example, the API could be interspersed between other paging channeltraffic at regularly-occurring intervals including, but not limited to,approximately every 1.28 seconds, approximately every 2 seconds orotherwise. In embodiments, the API can be transmitted at predeterminedtime slots to reduce the likelihood that a UE 220 will not receive theAPI. A longer API (e.g., an API having computer-readable address and ahuman-readable address) could be broadcast every 10 seconds, forexample, while a shorter API (e.g., an API having a computer-readableaddress but not having a human-readable address) could be broadcast atgreater time intervals. For example, shorter APIs could be broadcastevery approximately 1.28 seconds or approximately 2 seconds.

In various embodiments, the time intervals for transmitting the API canbe randomly-determined, fixed, dynamic and/or configurable. For example,a network operator can transmit to the AP 210 information regarding thetime interval over which or during which to transmit the AP.

In various embodiments, any time intervals can be used generallyfollowing the principle that the computer-readable address is morecritical information than the human-readable address. As such, in oneembodiment wherein different types of APIs are broadcast, each APIbroadcast contains a computer-readable address (in addition to or inlieu of other types of addresses identifying the AP 210). More criticalinformation (e.g., a computer-readable address) can be transmitted morefrequently than less critical information (e.g., a human-readableaddress) in various embodiments.

The channel on which the API is broadcast and/or the intervals at whichthe broadcasts occur can be fixed or change over time. Further, thechannel and/or the intervals for broadcasting the API can be programmedinto the AP 210 prior to or at the time of purchase or after purchase.For example, such information could be configured by OTA signaling. Forexample, the mobile operator core network could determine the intervalsat broadcasting and/or update the intervals or channels based on anynumber of factors, including, but not limited to, traffic conditions,channel conditions, etc.

The receiver module 330 can be configured to receive from the UE 220information for attempting acquisition of the AP 210. In someembodiments, the receiver module 330 can be configured to receive afirst signal including a registration request from a UE 220 proximate toa geographical area covered by the AP 210.

The processor module 340 can be communicatively coupled to thetransmitter module 320, the receiver module 330, the database module 310and the memory module 350. The processor module 340 can be configured tofacilitate identification and/or acquisition of the AP 210 (and/orhandoff to or from other APs or networks). In some embodiments, theprocessor module 340 can access one or more codes stored on acomputer-readable medium (such as could be stored as part of the memorymodule 350) for facilitating the identification and/or acquisition. Insome embodiments, the processor module 340 can include any hardware,software and/or a combination of hardware and software for facilitatingidentification and/or acquisition of AP 210 (and/or handoff to or fromother APs or networks) as described herein.

In various embodiments, the processor module 340 can be configured togenerate the API (or APIDM) and control the transmitter module 320 tobroadcast the API. The API can be broadcasted in the APIDM or in anyother signal able to be received by the UE 220.

The processor module 340 can also be configured to compare the storedinformation indicative of the one or more UEs 220 permitted to accessthe AP 210, with a UE requesting registration with the AP 210 inresponse to the transmitted APIDM. As noted above, the informationindicative of the one or more UEs 220 permitted to access the AP 210 canbe stored in the database memory 310. In response to finding a matchbetween the requesting UE and the information indicative of the one ormore UEs 220 permitted to access the AP 210, the processor module 340can control the AP 210 to provide access to the UE 220. By contrast, inresponse to finding no match between the requesting UE and theinformation indicative of the one or more UEs 220 permitted to accessthe AP 210, the processor module 340 can control the AP 210 to notprovide access to the UE 220.

In some embodiments, the processor module 340 can be configured toexecute codes stored on a computer-readable medium that can beassociated with the memory module 350, for example. Thecomputer-readable medium could store codes on the computer-readablemedium that, when executed by the processor module 340, cause the AP 210to perform selected functions. A first set of codes could be for causingthe AP 210 to transmit the API indicative of an identification of the AP210. A second set of codes could be for causing the AP 210 to receive,using the receiver module 330, information indicative of a registrationrequest from a UE 220 in response to transmitting the API. Theregistration request could be transmitted when the UE 220 determinesthat the AP 210 is a permitted access point (“PAP”). As used herein, theterm “PAP” shall mean an AP that the UE 220 is permitted to access. Insome embodiments, a third set of codes could be for determining whetherthe UE 220 is authorized to receive access to the AP 210, and a fourthset of codes could be for causing the AP 210 to provide access for theUE 220 to register with the AP 210. In some embodiments, access could beprovided in response to receiving the registration request from the UE220 and determining that the UE 220 is authorized to receive access tothe AP 210. Further, in various embodiments in which handoff must beperformed to the AP 210 from a macro network, the methodslater-described with reference to FIG. 9A and FIGS. 10A and 10B can beused.

FIG. 4A illustrates another exemplary block diagram of an access pointaccording to an embodiment. The AP 400 can include means fortransmitting 410 an API indicative of an identification of the AP 400.In various embodiments, the means for transmitting 410 can include, butis not limited to, a transmitter, a transceiver or a transmitter module,such as that described with reference to FIG. 3 as transmitter module320. The AP 400 can also include means for receiving 420 a registrationrequest from a UE 220 in response to transmitting the API. In variousembodiments, the means for receiving 420 can include, but is not limitedto, a receiver, a transceiver or a receiver module, such as thatdescribed with reference to FIG. 3 as receiver module 330. Theregistration request can be transmitted to the AP 400 from the UE 220 ifthe UE 220 determines that the AP 400 is a PAP. The AP 400 can alsoinclude means for permitting 430 the user equipment to access theapparatus in response to receiving the information indicative of theregistration request. In some embodiments, the means for permitting 430the user equipment to access the apparatus includes means fordetermining (not shown) whether the UE 220 is authorized to receiveaccess to the AP 400 and means for providing (not shown) access for theUE 220 in response to determining that the UE 220 is authorized toreceive access to the AP 400. In various embodiments, the means forpermitting 430, the means for determining whether the UE is authorizedto receive access to the AP 400 and/or the means for providing accesscan include, but is not limited to, a processor or a processor module,such as that described with reference to FIG. 3 as processor module 340.

Numerous methods for facilitating and/or acquisition of an AP can beprovided. By way of example, but not limitation, in some embodiments, amethod can include a sole step of facilitating identification andacquisition of an AP by transmitting an API indicative of anidentification of the AP. The API can be transmitted to a UE ingeographic proximity to the AP.

FIG. 4B illustrates another exemplary block diagram of an access pointaccording to an embodiment. The AP 400′ can include an electricalcomponent for transmitting 440 an API indicative of an identification ofthe AP 400′. The AP 400′ can also include an electrical component forreceiving 450 a registration request from a UE 220 in response totransmitting the API. The registration request can be transmitted to theAP 400′ from the UE 220 if the UE 220 determines that the AP 400′ is aPAP. The AP 400′ can also include an electrical component for permitting460 the user equipment to access the apparatus in response to receivingthe information indicative of the registration request. In someembodiments, the means for permitting 460 the user equipment to accessthe apparatus includes means for determining whether the UE 220 isauthorized to receive access to the AP 400′ and providing access for theUE 220 in response to determining that the UE 220 is authorized toreceive access to the AP 400′.

FIG. 5 illustrates an exemplary flowchart of a method for facilitatingidentification and/or acquisition of an AP according to embodiments. Insome embodiments, methods can include any of the processes and/orfunctions described above for identification and acquisition of the AP210 with reference to FIGS. 3, 4A and/or 4B (and can include any one ormore of such described features). In some embodiments, the method 500can include executing a hardware, software, a combination of hardwareand software, and/or specialized circuitry or computer code to performone or more of the steps of method 500. For example, method 500 caninclude executing a processor for performing one or more of the steps ofmethod 500. In some embodiments, the method 500 is as described below.

At 510, an API can be transmitted. The API can be of any form describedabove with reference to FIGS. 2A, 3, 4A and/or 4B. For example, invarious embodiments, the API can be configured by a user of the AP 210,a user of a UE 220 associated with the AP 210 and/or by a networkoperator from a location remote from the AP associated with the API. Byway of example, but not limitation, the network operator could provideinformation for configuring the API through Over-The-Air (“OTA”)signaling. Still, in some embodiments, the API can be hardwired orotherwise associated with or stored in the AP 210 at or prior to thetime of purchase of the AP 210. Yet still, in various embodiments, theAPI for a selected AP 210 could be configurable, fixed or dynamic. Forexample, the API could change over time. The factors determining whetherand when the API changes could include, but are not limited to, theamount of time that the API has been the same, the arrival of new APs210 in close proximity to the AP 210, user choice and/or user or networkoperator selection of a new or previously-used API or the like.

As another example, in various embodiments, the API can include acomputer-readable address, a human-readable address, an MSI_ID, and aCell_ID. In some embodiments, the API can include a computer-readableaddress, a human-readable address, an MSL_ID, and a Cell_ID, a Base_ID,an SID, an and/or information indicative of a latitude, longitude and/oraltitude. With reference to FIGS. 2A, 2B, 3, 4A and/or 4B, thecomputer-readable address, a human-readable address, an MSL_ID, and aCell_ID, a Base_ID, an SID, an and/or information indicative of alatitude, longitude and/or altitude can be associated with the AP 210 orthe AP 400.

In various embodiments, the API can be interspersed on a paging channel.The API can be transmitted at any predetermine time intervals or timeslots including, but not limited to, every message every approximately1.28 seconds (e.g., for an SCI of 0), every approximately 2.0 seconds(e.g., for an SCI of 1), every approximately 10 seconds or otherwise.

The time intervals can be fixed, configurable and/or variable and can bepermanent or changed from time to time. The channel or time intervals orlength or type of API transmitted can be transmitted based oninformation programmed prior to or at the time of purchase of amechanism for transmitting the API and/or after provisioning ofcorresponding configuration information that can be provided via OTAsignaling. As such, in some embodiments, as described above,configuration information is received for associating the transmitter ofthe API with the AP prior to transmitting the API.

In some embodiments, the API can be broadcast in a new message,including, but not limited to, a Sector Identification Message. In someembodiments, the API can be transmitted in an existing message on thepaging channel (e.g., a System Parameter Message on the paging channelfor cdma2000 1×RTT or a Sector Parameter Message on the paging channelfor cdma2000 1×EV-DO).

At 520, the transmitter of the API can receive information indicative ofa registration request from a recipient of the API permitted to accessthe transmitter of the API, and does not receive a registration requestfrom a recipient of the API not permitted to access the transmitter ofthe API. In some embodiments, the information indicative of theregistration request is received only after confirmation that thetransmitter of the information has confirmed that the transmitter ispermitted to access the recipient of the information indicative of theregistration request.

With reference to FIGS. 2A, 2B, 3, 4A and/or 4B, the informationindicative of the registration request can be received from a UE 220 ingeographic proximity to an AP 210, 400 for which the AP 210, 400 is aPAP. As such, in some embodiments, the method 500 can include processesfor reducing battery power expended by the AP 210, 400 (in the case of amobile AP that uses battery power) and/or traffic to the AP 210, 400 tothat which is caused by a registration request initiated by a UE 220permitted to access the AP 210, 400.

At 530, access can be provided to the transmitter of the informationindicative of the registration request. With reference to FIGS. 2A, 2B,3, 4A and/or 4B, access can be provided by the AP 210, 400.

It is assumed that the transmitter will only can transmit informationindicative of the registration request after confirming that thetransmitter is authorized to access the transmitter of the API and willnot transmit information indicative of the registration request if thetransmitter is not authorized to access the transmitter of the API.However, in some embodiments, information indicative of the registrationrequest can be received from a transmitter that is not permitted access.In such embodiments, the method 500 can also include, prior to 530wherein access is provided, the transmitter of the API confirming thatthe transmitter of the information indicative of the registrationrequest is permitted access. In such embodiments, referring to FIGS. 2A,2B, 3, 4A and/or 4B, the method 500 can also include an AP 210 thatreceives the information indicative of the registration request,comparing the information indicative of the identities of the UEs 220 towhich access is permitted with the identity of the UE 220 from which theinformation indicative of the registration request is received todetermine whether the UE 220 is permitted access.

FIG. 6 illustrates an exemplary block diagram of user equipmentaccording to an embodiment. With reference to FIGS. 3, 4A, 4B, 5 and/or6, an exemplary embodiment of the UE 220 will now be described. The UE220 can include a UE database module 610, a UE receiver module 620, a UEprocessor module 630, a UE transmitter module 640, a UE input module650, a UE memory module 670 and/or a UE filtering module 680. In someembodiments, the UE 220 can also include a display module 660. The UEdatabase module 610 can be communicatively coupled to the UE processormodule 630, which can be communicatively coupled to the UE memory module670. The UE processor module 630 can be communicatively coupled to theUE receiver module 620, the UE transmitter module 640, the UE memorymodule 670 and the UE filtering module 680.

In one or more embodiments, the UE 220 is configured to facilitateidentification and/or acquisition of an AP 210 to that is a PAP for theUE 220. In embodiments, the UE 220 can be configured to attemptacquisition of the AP 210 by if the AP 210 is a PAP. By contrast, the UEcan be configured to forgo attempting to access the AP 210 if the AP isnot a PAP. If the UE 220 is not permitted to access the AP 210, the UE220 may optionally continue an ongoing call, or initiate a new call,with another nearby AP or a cellular network.

The UE memory module 670 can include any number of different types ofmemory for facilitating identification and/or acquisition of an AP 210.By way of example, but not limitation, the memory module 350 can be aread-only memory, a read-write memory and/or a memory card storing oneor more different types of information about the AP 210 including, butnot limited to, one or more API for one or more APs 210. The API can beany type or length of API, broadcasted on any channel and/or at anypredetermined time intervals as described above with reference to FIGS.3, 4A, 4B and/or 5.

The UE memory module 670 can also store information for performinghandoff between the AP 210 and another AP (or a network), including, butnot limited to, the MSC_ID, the Cell_ID, an SID, a Base_ID, an NID,information received in an NLM, a GLM, an APIDM or otherwise. By way ofexamples, but not limitation, as discussed above with reference to FIGS.3, 4A, 4B and/or 5, in addition to an API for an AP 210, the UE memorymodule 670 can store information indicative of frequencies on which oneor more AP 210 transmits, radio technologies, etc.

In some embodiments, when only selected frequency bands can be used, theNLM can include information indicative of a plurality of frequency bandsand/or pseudo noise (“PN”) offsets of vertical (e.g., differentfrequency) AP neighbors, and horizontal (e.g., same frequency) APneighbors. The UE 220 can scan for APs using such information. Referringto FIG. 2A, the mobile operator core network 250 can configure the NLMto broadcast this scan/deployment information within each geographicregion and/or from each AP 210. In some embodiments, when the AP is afemto cell, the scan can be a femto scan. As such, the UE 220 would notneed to be pre-configured with the scan information. Such could beparticularly useful when the UE 220 is roaming.

In embodiments when all available frequency bands can be used, the NLMneed not specify frequency information. In these embodiments, the UEmemory module 670 can store acquisition table information associatedwith the geographical region indicator (“GEO”) of operation. If thecurrent GEO of operation is not know, such as when the UE 220 goes outof service after receiving an NLM, the UE 220 can scan all of thechannels in the acquisition table.

In some embodiments, the NLM information can be processed by the UEprocessor module 630 to aid the UE 220 in manual scans and/or initialacquisition of APs.

In some embodiments, the UE memory module 670 can store the NLMinformation once it acquires the information and the UE 220 can use thestored information to scan for APs when no macro coverage is available.In other embodiments, the UE 220 can use the scan information that ispreviously-stored in the UE memory module 670 to optimally scan for APs.The UE 220 can do employing better system re-identification (“BSR”) witha preferred roaming list (“PRL”) that can also be stored on the UEmemory module 670. The PRL method is defined in 3GPP2 C.S0016,“Over-The-Air-Service-Provisioning Specification,” TIA-683).

The BSR with PRL can control the APs to which a UE 220 can access basedon the frequencies and pseudo noise sequences (“PNs”) associated withthe APs in the geographic area in which the UE 220 is located.

The UE memory module 670 information can be stored in the UE memorymodule 670 prior to or at the time of purchase and/or stored uponreceipt of configuration information through OTA signaling. Withreference to FIG. 2A, for example, the UE memory module 670 can storeinformation received from the mobile operator core network 250 (e.g.,Sprint, Nextel) through OTA signaling to/from the mobile operator corenetwork 250. By way of example, but not limitation, the configurationinformation through OTA signaling (or through manual or otherconfiguration at or at a location proximate to the UE 220) that can bestored in the UE memory module 670 can be any information for operatingthe UE 220 and/or for facilitating identification and/or acquisition ofthe AP 210 (or any other AP or network to which the UE 220 cancommunicate). By way of example, but not limitation, the UE memorymodule 670 can store information indicative of the identity of the UEand/or information indicative of radio technology specifications bywhich the UE communicates.

The UE database module 610 can be communicatively coupled to the UEmemory module 670 and can store one or more different types ofinformation for facilitation of identification and/or acquisition of theAP 210 and/or for handoff to or from other APs (or networks). Forexample, the UE database module 610 can store information indicative ofthe identity of one or more APs that it is permitted (or not permitted)to access. In some embodiments, the information indicative of the APsthat the UE 220 is permitted to access can be stored in a white listwhile the APs that the UE 220 is not permitted to access can be storedin a black list. In some embodiments, the white list and the black listare not stored in the UE database module 610. Rather, the informationindicative of the white list and the black list are stored in a locationremote from the UE 220 and merely accessible by the UE 220 over acommunication channel or otherwise.

As another example, the UE database module 610 can store the informationindicative of terms of access for the AP 210. As another example, the UEdatabase module 610 can store information indicative of PUZL entries fora geographical region in which the UE 220 is located. The PUZL entriescan be used by the UE 220 to determine which AP to access, of any numberof APs that the UE 220 is permitted to access in a geographical area. Asother examples, the database module 610 can store information aboutother APs (or networks) other than the AP from which the UE 220 hasreceived an API. Information about the other APs (or networks) can beused to perform handoff. In some embodiments, the handoff can beperformed according to the methods described below with reference toFIGS. 9A and 9B.

The UE receiver module 620 can be disposed to receive an API (includedin an APIDM, a System Parameter Message on the paging channel forcdma2000 1×RTT, a Sector Parameter Message on the paging channel forcdma2000 1×EV-DO or otherwise, according to the system with which the UE220 is configured to operate). In one embodiment, the UE receiver module620 can be configured to receive, and the UE processor module 630configured to process, an MSC_ID and cell_ID of an AP 210 (in additionto an API of the AP 210) that is a target of the UE 220 during an activecall handoff.

The UE processor module 630 can be coupled to the UE filter module 680,the UE receiver module 620 and the UE database module 610. In oneembodiment, the UE processor module 630 can be configured to compare theAPI received by the UE receiver module 620 from an AP 210 with the APIsstored on the white list (or the black list) associated with the UE 220to determine whether the UE 220 is permitted (or not permitted) toaccess the AP 210. In one embodiment, if the API corresponds toinformation on the white list associated with the UE 220, the UEprocessor module 630 controls the UE transmitter module 640 to attemptacquisition of the AP 210. By contrast, if the API corresponds toinformation on the black list associated with the UE 220 (or if the UEcompares only the white list of the UE 220 to the API and the API doesnot correspond to any information on the white list), the UE processormodule 630 controls the UE transmitter module 640 such that no attemptat acquisition of the AP 210 is made by the UE 220. In otherembodiments, the UE 220 can similarly check the black list to which itis associated as a first (or only resort) to determine whether the UE220 is permitted to access the AP 210. As such, the UE 220 can reducethe use of battery power expended to access an AP 210 to which it is notpermitted to access.

In some embodiments, the UE filter module 680 masks a portion of the APIreceived at the UE receiving module 620 such that the UE processormodule 630 compares with the UE 220 black list (or white list) only theportion of the API that is unmasked. For example, in some embodiments,the API can include a first portion that is a subnet identifierindicative of a common enterprise to which the AP 210 is affiliated, anda second portion that is an AP identifier indicative of the AP withinthe subnet. The subnet identifier can have a fewer number of bits thanthe AP identifier. The UE filter module 680 can filter the API such thatthe portion of the API corresponding to the subnet identifier iscompared by the UE processor module 630 with the UE 220 black list (orwhite list). As such, processing power expended by the UE 220 to processAPIs can be reduced as the UE 220 can determine whether the AP 210 isnot a permitted AP based on processing only the portion of the APIcorresponding to the subnet identifier to which the AP 210 isaffiliated. By contrast, in some embodiments, if the portion of the APIis on the white list, the UE 220 can attempt acquisition of any AP fromwhich it is receiving an API in the geographical area that is affiliatedwith the subnet. The masked version of the API, can be an AP subnet ID,similar to that of an EV-DO subnet ID.

In some embodiments, the UE processor module 630 can be configured toexecute codes stored on a computer-readable medium that can beassociated with the UE memory module 670, for example. Thecomputer-readable medium could store codes on the computer-readablemedium that, when executed by the UE processor module 630, cause the UE220 to perform selected functions. A first set of codes could be forcausing the UE 220 to receive API indicative of an identification of anAP 210. The computer-readable medium can also include a second set ofcodes for causing the UE 220 to attempt acquisition of the AP 210 inresponse to determining that the AP 210 is a PAP. The computer-readablemedium can also include a third set of codes for causing the UE 220 tofail to attempt acquisition of the AP 210 in response to determiningthat the AP 210 is not a PAP.

The UE input module 650 could be communicatively coupled to the UEprocessor module 630 and the UE display module 660. The UE input module650 can be configured to receive manual input at the UE 220 forcontrolling the configuration and/or operation of the UE 220. Forexample, in cases when the API received at the UE receiver module 620includes a text string or other human-readable information, the UEdisplay module 660 can display the identity of the AP 210 thattransmitted the API and the input module 650 can receive inputs forupdating the black or white list with the API, selecting the API orotherwise.

Referring back to the UE processor module 630, in some embodiments, theUE processor module 630 is also configured to execute commands formodifying a pilot signal measurement message (“PSMM”) generated by theUE 220. The PSMM can include information indicative of the MSC_ID andthe Cell_ID. The UE transmitter module 640 can be configured to transmitthe modified PSMM for use during handoff.

In other embodiments, a second message can be generated by the UE 220.In these embodiments, in lieu of the PSMM including the MSC_ID and theCell_ID, the second message can include the MSC_ID and the Cell_ID. Thesecond message can be a supplemental or companion message to the PSMM.By way of example, but not limitation, the second message can be aHandoff Supplementary Information Notification Message (“HSINM”).

In various embodiments, the UE processor module 630 can be configured tofacilitate idle handoff, active handoff and/or AP discovery.

FIG. 7A illustrates another exemplary block diagram of user equipmentaccording to an embodiment. The UE 700 can include means for receiving710 API indicative of an identification of an access point (not shown).In various embodiments, the means for receiving 710 can include, but isnot limited to, a receiver, a transceiver or a receiver module, such asthat described with reference to FIG. 6 as the UE receiver module 620.The UE 700 can also include means for masking 720 a portion of the API.In various embodiments, the means for masking 720 can include, but isnot limited to, a filter or a UE filter module, such as that describedwith reference to FIG. 6 as UE filter module 680. The UE 700 can alsoinclude means for comparing 730 the unmasked portion of the API withinformation indicative of identities of one or more access points towhich access by the UE 700 is authorized. In various embodiments, themeans for comparing 730 can include, but is not limited to, a processor,a comparator or a processor module, such as that described withreference to FIG. 6 as UE processor module 630. The UE 700 can alsoinclude means for attempt to register 740 with the UE 700 if theunmasked portion of the API is indicative of the access point (notshown) being a PAP. In various embodiments, the means for attempting toregister 740 can include, but is not limited to, a transmitter, atransceiver or a transmitter module, such as that described withreference to FIG. 6 as UE transmitter module 640. In some embodiments,the UE 700 can include means for preventing (not shown) the UE 700 fromattempting to register with the access point if the access point is nota PAP. In various embodiments, the means for preventing can include, butis not limited to, a processor or a processor module, such as thatdescribed with reference to FIG. 6 as UE processor module 630.

FIG. 7B illustrates another exemplary block diagram of user equipmentaccording to an embodiment. The UE 700′ can include an electricalcomponent for receiving 750 API indicative of an identification of anaccess point (not shown). The UE 700′ can also include an electricalcomponent for masking 760 a portion of the API. The UE 700 can alsoinclude an electrical component for comparing 770 the unmasked portionof the API with information indicative of identities of one or moreaccess points to which access by the UE 700′ is authorized. The UE 700′can also include an electrical component for attempt to register 780with the UE 700′ if the unmasked portion of the API is indicative of theaccess point (not shown) being a PAP. In some embodiments, the UE 700′can include an electrical component for preventing (not shown) the UE700′ from attempting to register with the access point if the accesspoint is not a PAP.

FIG. 8 illustrates an exemplary flowchart of a method for facilitatingacquisition of an access point according to an embodiment. The methodsdescribed herein can use any of the one or more functions described tobe performed by the UE with reference to FIGS. 3, 4A, 4B, 5, 6, 7Aand/or 7B. In some embodiments, the method 800 can include executing ahardware, software, a combination of hardware and software, and/orspecialized circuitry or computer code to perform one or more of thesteps of method 800. For example, method 800 can include executing aprocessor for performing one or more of the steps of method 800. In someembodiments, method 800 is as follows.

At 810, an API can be received. Referring to FIGS. 2A, 2B, 3, 4 and/or5, the API can be received from an AP 210 providing communications in ageographic area in which the UE 220 is located.

At 820, in response to determining that the API received corresponds toan AP that is a PAP, acquisition of the AP can be attempted. As such, inresponse to determining that the API received does not correspond to anAP that is a PAP, acquisition of the AP is not attempted. In variousembodiments, determining that an API corresponds to an AP that ispermitted, can include comparing the API to information indicative ofidentities of one or more APs 210 to which access is authorized (and/ornot authorized). In some embodiments, masking the API is performed priorto comparing the API received to the information indicative ofidentities of one or more APs 210 to which access is authorized (and/ornot authorized).

At 830, information indicative of a registration request with the AP 210is transmitted if a determination is made that the AP from which the APIis received is a PAP. In some embodiments, as discussed above withreference to FIGS. 3, 4A, 4 b, 5, 6 and/or 7, the UE 220 can alsoattempt acquisition or not attempt acquisition based on a comparison ofthe API with PUZL entries for the UE 220, NLM, GNLM information, and/orany other information described herein to which the UE 220 has accessand/or with which the UE 220 can be configured.

FIG. 9A illustrates an exemplary embodiment of a call flow diagram ofhandoff of user equipment from a macro cell to an access point accordingto an embodiment. FIG. 9B illustrates an exemplary embodiment of a callflow diagram of handoff of user equipment from an access point to amacro cell according to an embodiment.

To perform handoff according to the embodiments described herein, insome embodiments, the UE 220 could transmit information indicative ofthe MSC_ID and the Cell_ID that it receives with the API to its sourcesector to establish a backhaul to prepare the network and the target APfor handoff. In some embodiments, the MSC_ID and the Cell_ID can betransmitted in a modified version of a pilot signal measurement message(“PSMM”). In other embodiments, a second message, in addition to, or inlieu of the PSMM can be transmitted by the UE 220. In these embodiments,in lieu of the PSMM including the MSC_ID and the Cell_ID, the secondmessage can include the MSC_ID and the Cell_ID. The second message canbe a supplemental or companion message to the PSMM. By way of example,but not limitation, the second message can be a handoff supplementaryinformation notification message (“HSINM”).

Turning first to FIG. 9A, the operations illustrated in the call flowdiagram can use signaling messages from 3GPP2 standards, although othersignaling messages from other standards can also be used. Below, thecall flow diagram variously references signaling messages and approachesused in the A.S0024, A.S0013, A.S0014, X.S0004-200 specifications forthe 3GPP2 standard. In the embodiment described below, the AP can be afemto AP such as femto AP 210, although the process can be employed fornumerous different types of APs.

At A, a call involving a UE can be in progress. In some embodiments, theUE can be the UE 220. At B, the Serving Base Station Controller (“BSC”)can determine if a handoff is required. If a determination is made thata handoff is required, the Serving BSC can transmit to the ServingMobile Switching Center (“Serving MSC”), a message indicating thathandoff is required. In one embodiment, the Handoff Required message canbe transmitted to the Serving MSC.

At C, the Serving MSC can determine if a handoff to a candidate FemtoConvergence Server (“FCS”) should be performed. The determination can bemade based on an IS-41 whole Cell Global Identification (“ICGI”)reported. At D, the Serving MSC can determine that the call at the UE220 should be handed off to the candidate (now target) FCS, and that thetarget FCS is not already on the call path. The Serving MSC can transmita Facilities Directive message (e.g., “FACDIR” message or “FACDIR2”message) to the target FCS, directing the target FCS to initiate aHandoff-Forward task. If the Serving MSC counts tandem segments, thenthe Serving MSC can increment a Segment Counter by one in the BillingIDparameter.

At E, the target FCS can determine the SIP address of the femto AP 210from the ICGI included in the FACDIR or FACDIR2 message and can look upthe associated Serving-Call Session Control Function (“S-CSCF”) andtransmit a handoff request, or a Handoff Required message encapsulatedusing a SIP: MESSAGE message. The target S-CSCF can forward the SIP:MESSAGE message to the target femto AP 210 through the Proxy-CallSession Control Function (“P-CSCF”).

In some embodiments, however, the ICGI can be reused by more than onefemto AP, and the target femto AP 210 can be identified by the ICGI whenit is unique for a given macro cell. Accordingly, in these embodiments,a source macro cell identifier can be used in combination with the ICGIto identify the target femto AP 210. The aforementioned embodiment is analternative to the process described at E, which uses only the ICGI toidentify the target femto AP 210.

Referring back to FIG. 9A, at F, the femto AP 210 can verify that the UE220 is allowed 1× cdma2000 circuit switched services through the femtoAP 210 and can transmit a SIP_INVITE message to the P-CSCF and then tothe S-CSCF. The S-CSCF can forward the SIP_INVITE message to the FCS.

At G, the FCS can request the Media Gateway (“MGW”) to set up anephemeral termination and can transmit a SIP_200 OK message along withthe Media Gateway Session Description Protocol (“MGW SDP”) to the S-CSCFand P-CSCF. The P-CSCF can forward the SIP_200_OK message to the femtoAP 210.

At H, upon receiving the SIP_200_OK message with the MGW SDP parameters,the femto AP 210 can set up the voice Real-Time Transport Protocol(“RTP”) bearer path to the MGW and can transmit to the P-CSCF and S-CSCFa SIP_MESSAGE message carrying the Handoff_Request_Ack message. TheS-CSCF can forward the message to the FCS.

At I, the necessary facilities on the designated target system can bemade available. Therefore, the target FCS can increase the SegmentCounter in the received BillingID parameter by one and use the newBillingID for the new call segment, return a FACDIR or FACDIR2 messageto the requesting MSC, and initiate a Handoff-Forward task.

At J, upon receiving the FACDIR or FACDIR2 message, the Serving MSC cantransmit a Mobile Handoff Order message to the served UE 220. A handoffcommand can be transmitted to the BSC and the BSC can transmit a handoffdirection message to the UE 220.

At K, the UE can be received on the designated traffic channel of thefemto AP 210. As such, voice channel acquisition is accomplished. At L,the target femto AP 210 can transmit a SIP_MESSAGE message carrying theHandoff Complete message to the P-CSCF and S-CSCF. The S-CSCF canforward the SIP_MESSAGE message carrying the Handoff Complete message tothe target FCS. At M, the target FCS can complete the voice path betweenthe traffic channel and the MSC-FCS trunk and can transmit a MobileStation On Channel (“MSONCH”) message to the initiator of theHandoff-Forward task (e.g., the Serving MSC), informing the requestingsystem that the target FCS has successfully completed theHandoff-Forward task. The Serving MSC, on receipt of the MSONCH, cancomplete the handoff process. In various embodiments, the MSC-FCS trunkshould be connected at this time if it has not already been connected.At N, a call is now in progress with the UE 220 through the femto AP210.

FIG. 9B illustrates an exemplary embodiment of a call flow diagram ofhandoff of user equipment from an access point to a macro cell accordingto an embodiment. To perform handoff according to the embodimentsdescribed herein, in some embodiments, the UE 220 could transmitinformation indicative of the MSC_ID and the Cell_ID that it receiveswith the API to its source sector to establish a backhaul to prepare thenetwork and the target femto AP 210 for handoff. In some embodiments,the MSC_ID and the Cell_ID can be transmitted in a modified version of apilot signal measurement message (“PSMM”). In other embodiments, asecond message, in addition to, or in lieu of the PSMM can betransmitted by the UE 220. In these embodiments, in lieu of the PSMMincluding the MSC_ID and the Cell_ID, the second message can include theMSC_ID and/or the Cell_ID. The second message can be a supplemental orcompanion message to the PSMM. By way of example, but not limitation,the second message can be an HSINM.

Turning to FIG. 9B, the operations illustrated in the call flow diagramcan use signaling messages from 3GPP2 standards, although othersignaling messages from other standards can also be used. Below, thecall flow diagram variously references signaling messages and approachesused in the A.S0024, A.S0013, A.S0014, X.S0004-200 specifications forthe 3GPP2 standard. In the embodiment described below, the AP is thefemto AP 210, although the process can be employed for numerousdifferent types of APs.

At A, a call involving the served UE 220 can be in progress through thefemto AP 210. For simplicity, it can be assumed that the serving FCS isthe anchor FCS for the duration of the call.

At B, the femto AP 210 can determine if a handoff is required and verifyan access node (“AN”) identified by the UE 220. At C, the femto AP 210can transmit a SIP_MESSAGE message including the Handoff Requiredmessage to the P-CSCF and S-CSCF. The S-CSCF can forward the SIP_MESSAGEmessage to the serving FCS.

At D, the Serving FCS can determine if a handoff to a candidate MSC isappropriate. This determination can be made based on the reported ICGI.The Serving MSC can determine that the call should be handed off to thecandidate (now target) MSC and that the target MSC is not already on thecall path. The Serving FCS can transmit an FACDIR or FACDIR2 message tothe target MSC, directing the target MSC to initiate a Handoff-Forwardtask. If the Serving FCS counts tandem segments, then the Serving FCScan increment the Segment Counter by one in the BillingID parameter.

Referring back to FIG. 9B, at E and F, the target MSC can prepare thetarget BSC for Handoff. At E, a Handoff Request can be transmitted fromthe target MSC to the target BSC. At F, a Handoff Request_Ack messagecan be transmitted from the target BSC to the target MSC. At G, thefacilities on the designated target system can be made available.Therefore, the target MSC can increase the Segment Counter in thereceived BillingID parameter by one and use the new BillingID for thenew call segment, return a FACDIR or FACDIR2 message to the requestingFCS, and initiate a Handoff-Forward task.

At H, upon receiving the FACDIR or FACDIR2 message, the Serving FCS cantransmit to the S-CSCF and P-CSCF a SIP_MESSAGE carrying the HandoffCommand. The P-CSCF can forward the SIP_MESSAGE to the femto AP 210.

At I, the femto AP 210 can order the UE 220 to handoff to the macro celland can transmit a SIP_MESSAGE message carrying the Handoff Commencedmessage to the P-CSCF and S-CSCF. At J, the S-CSCF can forward theSIP_MESSAGE message to the FCS.

At K, the UE 220 can be received on the designated traffic channel. Assuch, voice channel acquisition can be accomplished. At L and M, thetarget MSC can complete the voice path between the traffic channel andthe MSC-FCS trunk and, at N, the target MSC can transmit a MSONCH to theinitiator of the Handoff-Forward task (e.g., the Serving FCS), informingthe requesting system that the target MSC has successfully completed theHandoff-Forward task.

At O, the Serving FCS, upon receiving the MSONCH, can complete thehandoff process by transmitting a SIP_MESSAGE carrying the Clear Commandmessage to the femto AP 210 through the S-CSCF and P-CSCF. The FCS-MSCtrunk is connected at this time if it has not already been connected.

At P, the femto AP 210 can release the resources allocated to the UE 220that performed the handoff and can transmit a SIP_MESSAGE messagecarrying the Clear_Complete message. At Q, the voice call is now inprogress through the macro cell AN.

FIG. 9C illustrates an exemplary block diagram of a system forperforming handoff from a macro cell to a femto access point accordingto an embodiment. As shown with reference to FIG. 9C, the system 900 caninclude: means for receiving 910 transmitted handoff information from atarget AP. In various embodiments, the means for receiving 910 caninclude, but is not limited to, a receiver, a transceiver or a receivermodule, such as that described with reference to FIG. 6 as the UEreceiver module 620. The handoff information can include: informationindicative of an identity of a mobile switching center (“MSC_ID”) towhich the target AP is associated; and information indicative of anidentity of a cell to which the target access AP is associated. Thesystem 900 can also include: means for storing 920 the handoffinformation; and means for transmitting 930 the handoff information. Invarious embodiments, the means for storing 920 can include, but is notlimited to, a memory or memory module such as that described withreference to FIG. 6 as UE memory module 670. In various embodiments, themeans for storing 920 can also include, but is not limited to, adatabase or database module such as that described with reference toFIG. 6 as UE database module 610.

The system 900 can also include means for processing 940 the handoffinformation and controlling the means for transmitting 930 to transmitthe handoff information to initiate handoff to the target access point.In various embodiments, the means for processing 940 can include, but isnot limited to, a processor or processor module such as that describedwith reference to FIG. 6 as UE processor module 630. In variousembodiments, the means for transmitting 930 can include, but is notlimited to, a transmitter or transmitter module such as that describedwith reference to FIG. 6 as UE transmitter module 640.

FIGS. 10A and 10B illustrate first and second partial views of anexemplary embodiment of a call flow diagram of handoff of a mobilestation from a macro base station controller to a femto access pointaccording to an embodiment. FIG. 10A shows the call flow operations fromA to O while FIG. 10B shows the call flow operations from P to W. Thecomplete embodiment of FIGS. 10A and 10B can be provided by followingstep O with step P.

In various embodiments, the call flow illustrates exemplary steps thatcan be performed for mobile station (“MS”) handoff between the femtoaccess point (“femto AP 210”) and the macro base station controller(“Macro BSC”) when the MS is in the geographic vicinity of a femto AP210. In embodiments, the MS can be the UE 220, a system, device,subscriber unit, subscriber station, mobile, mobile device, remotestation, remote terminal, access terminal, user terminal, communicationdevice, user agent and/or a user device.

To perform handoff according to the embodiments described herein, insome embodiments, the MS could transmit information indicative of signalstrength measurements to establish a backhaul to prepare the network andthe target femto AP 210 for handoff. The signal strength measurementscould be included in a Pilot Strength Measurement (“PSM”) report. Insome embodiments, the MS could transmit a second message, in additionto, or in lieu of the PSM report. In these embodiments, the secondmessage can be a supplemental or companion message to the PSM report. Byway of example, but not limitation, the second message can be an HSINM.

The process illustrated in FIGS. 10A and 10B can be used for 1× voicecall handoff from a macro cell to a target femto AP 210. Turning now toFIG. 10A, the operations illustrated in the call flow diagram can usesignaling messages from 3GPP2 standards, although other signalingmessages from other standards can also be used. Below, the call flowdiagram variously references signaling messages and approaches used inthe X.P0059-200-0 v0.7 and C.S0005 specification for the 3GPP2 standard.

In the embodiment shown in FIGS. 10A and 10B, in some cases, thefollowing preconditions exist for successful handoff. There is anexisting voice path between the MS on the 1× macro network (“MS-MC”) anda Public Switched Telephone Network (“PSTN”) address through the 1×macro network base station (“Macro BS”) and (serving and/or anchoring)MSC.

At A, the MS can monitor the pilot signal strength for neighboringcells, including femto cells. In various embodiments, the MS can be aMS-MC and the macro cell can be represented by an entity such as a MacroBS. The MS can monitor the neighbor cell pilot strength. The MS cantransmit signal strength information to the macro cell. In someembodiments, the signal strength information can be the pilot signalstrength measurements (“PSMM”). In some embodiments, as described abovewith reference to FIG. 9A, the HSINM can be transmitted in lieu of or inaddition to the PSMM.

At B, the macro BS can determine that handoff to a femto AP 210 isnecessary, and can signal a Handoff Required message (and/or HandoffRequested message) to the MSC.

At C, the MSC can determine that the target cell is associated with theinformation indicative of an identity of the mobile switching center(“MSC_ID”) for the FCS and can transmit a Mobile Application Part (MAP)FacilityDirective2 (FACDIR2) message to the target FCS associated withthe target cell. In some embodiments, the MAP FACDIR2 message caninclude a Time Division Multiplexing Circuit Identifier (“TDM CircuitID”), a serving cell identifier and a target cell identifier.

The FCS can reserve the inter-vendor trunk (IVT) port that terminatesthe IVT identified in the FACDIR2 message. The FCS can also reserve theMGW resources required to terminate the RTP bearer path with the targetfemto AP 210 (note that the IVT and the MGW could be handled by aseparate Media Gateway Control Function (“MGCF”)).

At D, if a target femto AP 210 cannot be uniquely determined, the FCScan transmit a SIP MESSAGE with a measurement request for the MS. Themessage can be transmitted to the candidate femto AP that match thetarget cell information. In the embodiment shown in FIG. 10B, two femtoAPs (i.e., Femto AP1 and Femto AP2) are shown as possible candidates;however, it is possible to have more than two femto AP candidates. Assuch, at E, the FCS transmits a second SIP MESSAGE with a measurementreport to a second candidate femto AP. The SIP MESSAGE can include arequest that the candidate femto detect and measure MS signal strengthsfor the incoming handoff. As shown, in one embodiment, the SIP MESSAGEcan be transmitted to the CSCF first (steps D1, E1) and from the CSCF toFemto AP1 and Femto AP2 (steps D2, E2, respectively). In someembodiments, the SIP MESSAGE can be a MESSAGE (Femto APE MeasurementRequest) message at D1 and D2. In some embodiments, the SIP MESSAGE canbe a MESSAGE (Femto APs, Measurement Request) message at E1 and E2.

At F, G, H and I, the candidate femto AP can try to detect the MS andmeasure the signal strength of the MS uplink while the MS is engaged inan active voice call over the macro network. The candidate femto APs canrespond to the FCS with radio uplink signal strength measurements forthe MS in the SIP 200 OK responses to the FCS. As shown, the Femto AP1and Femto AP2 can transmit the measurements to the CSCF first (steps Fand H, respectively) and then from the CSCF to the FCS (steps G and I,respectively). In some embodiments, at F, G, H and/or I, themeasurements can be transmitted as 200 OK; MESSAGE (RL signal strength)messages.

The FCS can uniquely identify the selected target femto based on thesignal strength measurements of the MS reported by the candidate femtoAPs. In some embodiments, the Femto AP 1 is the selected target femtoAP.

The FCS can then transmit to the target femto AP a SIP INVITE with theMGW SDP offer and include the Content Type Handoff Request. The SIPINVITE can also include an identifier of the target femto AP. The SIPINVITE can first be transmitted to the CSCF (step J) and then from theCSCF to the target femto AP (step K). In some embodiments, the SIPINVITE can be an INVITE (target femto AP, Handoff Request, MGW SDP)message at J and K.

The femto AP can respond by transmitting an immediate 200 OK messagecontaining the femto AP SDP answer and include the content Type HandoffRequest Ack to the FCS. First, the 200 OK message can be transmitted tothe CSCF (step L) and then from the CSCF to the FCS (step M). At L andat M, the 200 OK message can be a 200 OK (femto AP SDP Answer, HandoffRequest ACK) message.

At N, the FCS can transmit back to the femto AP an acknowledgementmessage acknowledging receipt of the 200 OK message. The acknowledgementcan be transmitted first to the CSCF (step N) and then from the CSCF tothe femto AP (step O).

At this time the voice/bearer path through the IP Multimedia Subsystem(“IMS”) core network is established. In some embodiments, the path is anIP/RTP voice path.

Turning next to FIG. 10B, the process can continue. At P, the FCS canrespond to the MSC by transmitting to the MSC a MAP FACDIR2 returnresult. In some embodiments, the MSC to which the FCS transmits the MAPFACDIR2 return result can be an anchor MSC. The MAP FACDIR2 returnedresult can confirm the establishment of the IVT connection. At Q, theMSC can direct the MS via the macro BS to handoff to the target femto APby transmitting to the MS a Handoff Command.

At R, a Handoff complete message can be transmitted from the MS on thefemto cell network (“MS-FC”) to the femto AP, the MS can acquire theforward link traffic channel from the femto AP, and a voice path betweenthe MS and femto AP can be established.

The femto AP can notify the FCS that the handoff is complete via a SIPMESSAGE transmitted from the femto AP to the FCS. First, the SIP MESSAGEis transmitted to the CSCF (step S) and then from the CSCF to the FCS(step T).

At U, the FCS can signal the MSC that the MS has completed the handoffsuccessfully by transmitting to the MSC a MAP MSONCH Channel message. Insome embodiments, the MSC to which the FCS transmits the MAP MSONCHChannel message can be an anchor MSC.

The FCS can respond to the femto AP with a 200 OK acknowledgment ofreceipt of the SIP MESSAGE described above with reference to T. The 200OK acknowledgment is first transmitted to the CSCF (step V) and thenfrom the CSCF to the femto AP (step W).

FIGS. 10C and 10D illustrate first and second partial views of anexemplary embodiment of a call flow diagram of handoff of a mobilestation from a femto access point to a macro base station controlleraccording to an embodiment. FIG. 10C shows the call flow operations fromA to S while FIG. 10D shows the call flow operations from T to Z6. Thecomplete embodiment of FIGS. 10C and 10D can be provided by followingstep S with step T.

Turning now to FIGS. 10C and 10D, the operations illustrated in the callflow diagram can use signaling messages from 3GPP2 standards, althoughother signaling messages from other standards can also be used. Below,the call flow diagram variously references signaling messages andapproaches used in the X.P0059-200-0 v0.7, X.50004-200, A.S0013 andA.S0024 specification for the 3GPP2 standard.

The process illustrated in FIGS. 10C and 10D, can be used for 1× voicecall handoff from a femto AP to a target macro cell.

At A, the femto can receive the signal strength measurement. In variousembodiments, the signal strength measurement can be a Pilot StrengthMeasurement (“PSM”) report and/or an HSINM report from the MS. As notedabove, in some embodiments, the MS could transmit a second message, inaddition to, or in lieu of the PSM report. In these embodiments, thesecond message can be a supplemental or companion message to the PSMreport. By way of example, but not limitation, the second message can bean HSINM. The femto AP can use the PSM report to determine if a handoffis required and verifies the target cell identified by the MS isappropriate.

As noted above, in some embodiments, the MS could transmit a secondmessage, in addition to, or in lieu of the PSM report. In theseembodiments, the second message can be a supplemental or companionmessage to the PSM report. By way of example, but not limitation, thesecond message can be an HSINM.

Referring back to FIG. 10C, at B, the femto AP can transmit aSIP_MESSAGE with Content Type Handoff Required Message to the P-CSCFand/or S-CSCF. At C, the S-CSCF can forward the SIP_MESSAGE to theserving FCS.

At D and E, a SIP message can be transmitted. In particular at D, theFCS can transmit a SIP_202_Accept message to the S-CSCF acknowledgingreceipt of the SIP_MESSAGE from the transmission of the SIP_MESSAGEdescribed above at C. At E, the S-CSCF can forward this SIP_202_Acceptmessage to the femto AP.

The serving FCS can determine if a handoff to a candidate MSC (based onthe reported ICGI) is appropriate.

The Serving FCS can determine whether the call should be handed off tothe candidate (now target) MSC and that the target MSC is not already onthe call path. In F, the Serving FCS can transmit a FACDIR2 to thetarget MSC, directing the target MSC to initiate a Handoff-Forward task.If the Serving FCS counts tandem segments, then the Serving FCS canincrement the Segment Counter by one in the BillingID parameter.

At G and H, the target MSC can prepares the target AN for Handoff. Inparticular, at G, the target MSC can transmit a Handoff Request messageto the target BS and, at H, the target BS can transmit back to thetarget MSC a Handoff Request_ACK message.

At I, the necessary facilities on the designated target system aregenerally available. As such, the target MSC can increase the SegmentCounter in the received BillingID parameter by one and use the newBillingID for the new call segment, return a FACDIR2 message to therequesting FCS, and initiate a Handoff-Forward task.

At J, upon receipt of the FACDIR2, the Serving FCS can transmit to theS-CSCF and/or P-CSCF, a SIP_MESSAGE with the Content Type HandoffCommand. At K, the P-CSCF can forward the SIP_MESSAGE to the femto AP.

At L and M, a SIP message can be transmitted. In particular, at L, thefemto AP can transmit to the S-CSCF and/or the P-CSCF a SIP: 202 Acceptmessage acknowledging the receipt of the SIP_MESSAGE transmitted asdiscussed above at K. At M, the S-CSCF can forward the SIP: 202 Acceptmessage to the FCS.

At N, the femto AP can order the MS to handoff to the Macro BS. In someembodiments, traffic assignment and handoff initiation then commencesbetween the MS and the femto AP.

At O, the femto AP can transmit a SIP_MESSAGE with Content Type HandoffCommenced to the P-CSCF and/or S-CSCF. At P, the S-CSCF can forward theSIP_MESSAGE to the FCS.

At Q and R, a SIP message can be transmitted. In particular, at Q, theFCS can transmit to the S-CSCF a SIP: 202 Accept message acknowledgingthe receipt of SIP_MESSAGE as described above with reference to P. At R,the S-CSCF can forward the SIP: 202 Accept message to the femto APthrough the P-CSCF.

At S, the MS can receive communications on the designated trafficchannel. In some embodiments, the communications are voicecommunications, although other types of communications may also bereceived.

At T, the target BS can transmit to the target MSC, a Handoff CompleteMessage. At U, the target MSC can complete the voice path between thetraffic channel and the MSC-FCS trunk and can transmit a MSONCH messageto the initiator of the Handoff-Forward task, the Serving FCS, informingthe requesting system that the target MSC has successfully completed theHandoff-Forward task.

At V and/or at any step after the step described with reference to Labove, the Serving FCS can transmit a SIP_reINVITE to the Other EndPoint (“OEP”) with the SDP of the MGW the Serving FCS controls to setupthe bearer path between the OEP and the MGW instead of the femto AP.

At W, the OEP can transmit a SIP_200_OK to the FCS after re-pointing thebearer path from the OEP to the MGW controlled by the FCS instead of thefemto AP. At X, upon receipt of the MSONCH message as described abovewith reference to U, and a SIP_200_OK as described above with referenceto W, the FCS can complete the handoff process by transmitting aSIP_MESSAGE with the Content Type Clear_Command to the femto AP, and atY, to the S-CSCF and P-CSCF. In some embodiments, the FCS-MSC trunkshould be connected at this time if it has not already been connected.

At Z, the femto AP can transmit to the S-CSCF and/or the P-CSCF a SIP:202 Accept message acknowledging the receipt of SIP_MESSAGE describedabove with reference to V. At Z1, the S-CSCF can forward the SIP: 202Accept message to the FCS.

At Z2, the femto AP can release the resources allocated to the MS thatperformed the handoff and can transmit a SIP_MESSAGE with the ContentType Clear Complete to the P-CSCF and/or S-CSCF. At Z3, the S-CSCF canforward the SIP_MESSAGE to the FCS.

At Z4, the FCS can transmit to the S-CSCF a SIP: 202 Accept messageacknowledging the receipt of SIP_MESSAGE in step 24. At Z5, the S-CSCFcan forward the SIP: 202 Accept message to the femto AP through theP-CSCF. At Z6, the voice call can then be in progress through the targetMacro BS.

FIG. 11 illustrates an exemplary communication system that provides APidentification. Referring now to FIG. 11, a block diagram illustratingan example wireless communication system 1100 in which various aspectsdescribed herein can function is provided. In one example, system 1100is a multiple-input multiple-output (MIMO) system that includes atransmitter system 1100 and a receiver system 1150. It should beappreciated, however, that transmitter system 1100 and/or receiversystem 1150 could also be applied to a multi-input single-output systemwherein, for example, multiple transmit antennas (e.g., on a basestation), can transmit one or more symbol streams to a single antennadevice (e.g., a mobile station). Additionally, it should be appreciatedthat aspects of transmitter system 1100 and/or receiver system 1150described herein could be utilized in connection with a single output tosingle input antenna system.

In accordance with one aspect, traffic data for a number of data streamsare provided at transmitter system 1100 from a data source 1102 to atransmit (TX) data processor 1104. In one example, each data stream canthen be transmitted via a respective transmit antenna 1124.Additionally, TX data processor 1104 can format, encode, and interleavetraffic data for each data stream based on a particular coding schemeselected for each respective data stream in order to provide coded data.In one example, the coded data for each data stream can then bemultiplexed with pilot data using OFDM techniques. The pilot data canbe, for example, a known data pattern that is processed in a knownmanner. Further, the pilot data can be used at receiver system 1150 toestimate channel response. Back at transmitter system 1100, themultiplexed pilot and coded data for each data stream can be modulated(i.e., symbol mapped) based on a particular modulation scheme (e.g.,BPSK, QSPK, M-PSK, or M-QAM) selected for each respective data stream inorder to provide modulation symbols. In one example, data rate, coding,and modulation for each data stream can be determined by instructionsperformed on and/or provided by processor 1130.

Next, modulation symbols for all data streams can be provided to a TXprocessor 1120, which can further process the modulation symbols (e.g.,for OFDM). TX MIMO processor 1120 can then provides N_(T) modulationsymbol streams to N_(T) transceivers 1122 a through 1122 t. In oneexample, each transceiver 1122 can receive and process a respectivesymbol stream to provide one or more analog signals. Each transceiver1122 can then further condition (e.g., amplify, filter, and upconvert)the analog signals to provide a modulated signal suitable fortransmission over a MIMO channel. Accordingly, N_(T) modulated signalsfrom transceivers 1122 a through 1122 t can then be transmitted fromN_(T) antennas 1124 a through 1124 t, respectively.

In accordance with another aspect, the transmitted modulated signals canbe received at receiver system 1150 by N_(R) antennas 1152 a through1152 r. The received signal from each antenna 1152 can then be providedto respective transceivers 1154. In one example, each transceiver 1154can condition (e.g., filter, amplify, and downconvert) a respectivereceived signal, digitize the conditioned signal to provide samples, andthen processes the samples to provide a corresponding “received” symbolstream. An RX MIMO/data processor 1160 can then receive and process theN_(R) received symbol streams from N_(R) transceivers 1154 based on aparticular receiver processing technique to provide N_(T) “detected”symbol streams. In one example, each detected symbol stream can includesymbols that are estimates of the modulation symbols transmitted for thecorresponding data stream. RX processor 1160 can then process eachsymbol stream at least in part by demodulating, deinterleaving, anddecoding each detected symbol stream to recover traffic data for acorresponding data stream. Thus, the processing by RX processor 1160 canbe complementary to that performed by TX MIMO processor 1120 and TX dataprocessor 1115 at transmitter system 1100. RX processor 1160 canadditionally provide processed symbol streams to a data sink 1164.

In accordance with one aspect, the channel response estimate generatedby RX processor 1160 can be used to perform space/time processing at thereceiver, adjust power levels, change modulation rates or schemes,and/or other appropriate actions. Additionally, RX processor 1160 canfurther estimate channel characteristics such as, for example,signal-to-noise-and-interference ratios (SNRs) of the detected symbolstreams. RX processor 1160 can then provide estimated channelcharacteristics to a processor 1170. In one example, RX processor 1160and/or processor 1170 can further derive an estimate of the “operating”SNR for the system. Processor 1170 can then provide channel stateinformation (CSI), which can comprise information regarding thecommunication link and/or the received data stream. This information caninclude, for example, the operating SNR. The CSI can then be processedby a TX data processor 1138, modulated by a modulator 1180, conditionedby transceivers 1154 a through 1154 r, and transmitted back totransmitter system 1100. In addition, a data source 1136 at receiversystem 1150 can provide additional data to be processed by TX dataprocessor 1138.

Back at transmitter system 1100, the modulated signals from receiversystem 1150 can then be received by antennas 1124, conditioned bytransceivers 1122, demodulated by a demodulator 1140, and processed by aRX data processor 1142 to recover the CSI reported by receiver system1150. In one example, the reported CSI can then be provided to processor1130 and used to determine data rates as well as coding and modulationschemes to be used for one or more data streams. The determined codingand modulation schemes can then be provided to transceivers 1122 forquantization and/or use in later transmissions to receiver system 1150.Additionally and/or alternatively, the reported CSI can be used byprocessor 1130 to generate various controls for TX data processor 1104and TX MIMO processor 1120. In another example, CSI and/or otherinformation processed by RX data processor 1142 can be provided to adata sink 1144.

In one example, processor 1130 at transmitter system 1100 and processor1170 at receiver system 1150 direct operation at their respectivesystems. Additionally, database 1132 at transmitter system 1100 anddatabase 1172 at receiver system 1150 can provide storage for programcodes and data used by processors 1130 and 1170, respectively. Further,at receiver system 1150, various processing techniques can be used toprocess the N_(R) received signals to detect the N_(T) transmittedsymbol streams. These receiver processing techniques can include spatialand space-time receiver processing techniques, which can also bereferred to as equalization techniques, and/or “successivenulling/equalization and interference cancellation” receiver processingtechniques, which can also be referred to as “successive interferencecancellation” or “successive cancellation” receiver processingtechniques.

The teachings herein may be incorporated into a node (e.g., a device)employing various components for communicating with at least one othernode. FIG. 11 depicts several sample components that may be employed tofacilitate communication between nodes. Specifically, FIG. 11illustrates a wireless device 1110 (e.g., an access point) and awireless device 1150 (e.g., a UE) of a MIMO system 1100. At the device1110, traffic data for a number of data streams is provided from a datasource 1112 to a transmit (“TX”) data processor 1114.

In some aspects, each data stream is transmitted over a respectivetransmit antenna. The TX data processor 1114 formats, codes, andinterleaves the traffic data for each data stream based on a particularcoding scheme selected for that data stream to provide coded data.

The coded data for each data stream may be multiplexed with pilot datausing OFDM techniques. The pilot data is typically a known data patternthat is processed in a known manner and may be used at the receiversystem to estimate the channel response. The multiplexed pilot and codeddata for each data stream is then modulated (i.e., symbol mapped) basedon a particular modulation scheme (e.g., BPSK, QSPK, M-PSK, or M-QAM)selected for that data stream to provide modulation symbols. The datarate, coding, and modulation for each data stream may be determined byinstructions performed by a processor 1130. A data memory 1132 may storeprogram code, data, and other information used by the processor 1130 orother components of the device 1110.

The modulation symbols for all data streams are then provided to a TXMIMO processor 1120, which may further process the modulation symbols(e.g., for OFDM). The TX MIMO processor 1120 then provides N_(T)modulation symbol streams to N_(T) transceivers (“XCVR”) 1122A through1122T. In some aspects, the TX MIMO processor 1120 applies beam-formingweights to the symbols of the data streams and to the antenna from whichthe symbol is being transmitted.

Each transceiver 1122 receives and processes a respective symbol streamto provide one or more analog signals, and further conditions (e.g.,amplifies, filters, and upconverts) the analog signals to provide amodulated signal suitable for transmission over the MIMO channel. N_(T)modulated signals from transceivers 1122A through 1122T are thentransmitted from N_(T) antennas 1124A through 1124T, respectively.

At the device 1150, the transmitted modulated signals are received byN_(R) antennas 1152A through 1152R and the received signal from eachantenna 1152 is provided to a respective transceiver (“XCVR”) 1154Athrough 1154R. Each transceiver 1154 conditions (e.g., filters,amplifies, and downconverts) a respective received signal, digitizes theconditioned signal to provide samples, and further processes the samplesto provide a corresponding “received” symbol stream.

A receive (“RX”) data processor 1160 then receives and processes theN_(R) received symbol streams from N_(R) transceivers 1154 based on aparticular receiver processing technique to provide N_(T) “detected”symbol streams. The RX data processor 1160 then demodulates,deinterleaves, and decodes each detected symbol stream to recover thetraffic data for the data stream. The processing by the RX dataprocessor 1160 is complementary to that performed by the TX MIMOprocessor 1120 and the TX data processor 1114 at the device 1110.

A processor 1170 periodically determines which pre-coding matrix to use(discussed below). The processor 1170 formulates a reverse link messagecomprising a matrix index portion and a rank value portion. A datamemory 1172 may store program code, data, and other information used bythe processor 1170 or other components of the device 1150.

The reverse link message may comprise various types of informationregarding the communication link and/or the received data stream. Thereverse link message is then processed by a TX data processor 1138,which also receives traffic data for a number of data streams from adata source 1136, modulated by a modulator 1180, conditioned by thetransceivers 1154A through 1154R, and transmitted back to the device1110.

At the device 1110, the modulated signals from the device 1150 arereceived by the antennas 1124, conditioned by the transceivers 1122,demodulated by a demodulator (“DEMOD”) 1140, and processed by a RX dataprocessor 1142 to extract the reverse link message transmitted by thedevice 1150. The processor 1130 then determines which pre-coding matrixto use for determining the beam-forming weights then processes theextracted message.

FIG. 11 also illustrates that the communication components may includeone or more components that perform interference control operations astaught herein. For example, an interference (“INTER.”) control component1190 may cooperate with the processor 1130 and/or other components ofthe device 1110 to send/receive signals to/from another device (e.g.,device 1150) as taught herein. Similarly, an interference controlcomponent 1192 may cooperate with the processor 1170 and/or othercomponents of the device 1150 to send/receive signals to/from anotherdevice (e.g., device 1110). It should be appreciated that for eachdevice 1110 and 1150 the functionality of two or more of the describedcomponents may be provided by a single component. For example, a singleprocessing component may provide the functionality of the interferencecontrol component 1190 and the processor 1130 and a single processingcomponent may provide the functionality of the interference controlcomponent 1192 and the processor 1170.

The various illustrative logics, logical blocks, modules, and circuitsdescribed in connection with the embodiments disclosed herein may beimplemented or performed with a general purpose processor, a digitalsignal processor (DSP), an application specific integrated circuit(ASIC), a field programmable gate array (FPGA) or other programmablelogic device, discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. A general-purpose processor may be a microprocessor,but, in the alternative, the processor may be any conventionalprocessor, controller, microcontroller, or state machine. A processormay also be implemented as a combination of computing devices, e.g., acombination of a DSP and a microprocessor, a plurality ofmicroprocessors, one or more microprocessors in conjunction with a DSPcore, or any other such configuration. Additionally, at least oneprocessor may comprise one or more modules operable to perform one ormore of the steps and/or actions described above.

Further, the steps and/or actions of a method or algorithm described inconnection with the aspects disclosed herein may be embodied directly inhardware, in a software module executed by a processor, or in acombination of the two. A software module may reside in RAM database,flash database, ROM database, EPROM database, EEPROM database,registers, a hard disk, a removable disk, a CD-ROM, or any other form ofstorage medium known in the art. An exemplary storage medium may becoupled to the processor, such that the processor can read informationfrom, and write information to, the storage medium. In the alternative,the storage medium may be integral to the processor. Further, in someaspects, the processor and the storage medium may reside in an ASIC.Additionally, the ASIC may reside in a user terminal. In thealternative, the processor and the storage medium may reside as discretecomponents in a user terminal. Additionally, in some aspects, the stepsand/or actions of a method or algorithm may reside as one or anycombination or set of codes and/or instructions on a machine-readablemedium and/or computer readable medium, which may be incorporated into acomputer program product.

In one or more exemplary embodiments, the functions described may beimplemented in hardware, software, firmware, or any combination thereof.If implemented in software, the functions may be stored on ortransmitted over as one or more instructions or code on acomputer-readable medium. Computer-readable media includes both computerstorage media and communication media including any medium thatfacilitates transfer of a computer program from one place to another. Astorage media may be any available media that can be accessed by acomputer. By way of example, and not limitation, such computer-readablemedia can comprise RAM, ROM, EEPROM, CD-ROM or other optical diskstorage, magnetic disk storage or other magnetic storage devices, or anyother medium that can be used to carry or store desired program code inthe form of instructions or data structures and that can be accessed bya computer. Also, any connection is properly termed a computer-readablemedium. For example, if the software is transmitted from a website,server, or other remote source using a coaxial cable, fiber optic cable,twisted pair, digital subscriber line (DSL), or wireless technologiessuch as infrared, radio, and microwave, then the coaxial cable, fiberoptic cable, twisted pair, DSL, or wireless technologies such asinfrared, radio, and microwave are included in the definition of medium.Disk and disc, as used herein, includes compact disc (CD), laser disc,optical disc, digital versatile disc (DVD), floppy disk and blu-ray discwhere disks usually reproduce data magnetically, while discs reproducedata optically with lasers. Combinations of the above should also beincluded within the scope of computer-readable media.

In one or more aspects, the functions described may be implemented inhardware, software, firmware, or any combination thereof. If implementedin software, the functions may be stored or transmitted as one or moreinstructions or code on a computer-readable medium. Computer-readablemedia includes both computer storage media and communication mediaincluding any medium that facilitates transfer of a computer programfrom one place to another. A storage medium may be any available mediathat can be accessed by a computer. By way of example, and notlimitation, such computer-readable media can comprise RAM, ROM, EEPROM,CD-ROM or other optical disk storage, magnetic disk storage or othermagnetic storage devices, or any other medium that can be used to carryor store desired program code in the form of instructions or datastructures and that can be accessed by a computer. Also, any connectionmay be termed a computer-readable medium. For example, if software istransmitted from a website, server, or other remote source using acoaxial cable, fiber optic cable, twisted pair, digital subscriber line(DSL), or wireless technologies such as infrared, radio, and microwave,then the coaxial cable, fiber optic cable, twisted pair, DSL, orwireless technologies such as infrared, radio, and microwave areincluded in the definition of medium. Disk and disc, as used herein,includes compact disc (CD), laser disc, optical disc, digital versatiledisc (DVD), floppy disk and blu-ray disc where disks usually reproducedata magnetically, while discs usually reproduce data optically withlasers. Combinations of the above should also be included within thescope of computer-readable media.

While the foregoing disclosure discusses illustrative aspects and/orembodiments, it should be noted that various changes and modificationscould be made herein without departing from the scope of the describedaspects and/or embodiments as defined by the appended claims.Furthermore, although elements of the described aspects and/orembodiments may be described or claimed in the singular, the plural iscontemplated unless limitation to the singular is explicitly stated.Additionally, all or a portion of any aspect and/or embodiment may beutilized with all or a portion of any other aspect and/or embodiment,unless stated otherwise.

What is claimed is:
 1. A method for performing handoff to a targetaccess point, the method comprising: transmitting, by user equipment,handoff information received from the target access point, the handoffinformation comprising: information indicative of an identity of amobile switching center to which the target access point is associated;and information indicative of an identity of a cell to which the targetaccess point is associated.
 2. The method of claim 1, wherein thehandoff information is transmitted within a handoff supplementaryinformation notification message (“HSINM”).
 3. The method of claim 1,wherein the handoff information is transmitted within a pilot signalmeasurement message.
 4. The method of claim 1, further comprisingperforming handoff to the target access point.
 5. The method of claim 1,wherein the target access point is a femto access point.
 6. A tangiblecomputer-program product, comprising: a non-transitory computer-readablemedium comprising: code for causing a computer to transmit handoffinformation received from a target access point, the handoff informationcomprising: information indicative of an identity of a mobile switchingcenter to which the target access point is associated; and informationindicative of an identity of a cell to which the target access point isassociated.
 7. The tangible computer-program product of claim 6, whereinthe handoff information is transmitted within a handoff supplementaryinformation notification message (“HSINM”).
 8. The tangiblecomputer-program product of claim 6, wherein the handoff information istransmitted within a pilot signal measurement message.
 9. The tangiblecomputer-program product of claim 6, wherein the non-transitorycomputer-readable medium further comprises code for causing the computerto perform handoff to the target access point.
 10. The tangiblecomputer-program product of claim 6, wherein the target access point isa femto access point.
 11. An apparatus comprising: a receiver moduleconfigured to receive transmitted handoff information from a targetaccess point, the handoff information comprising: information indicativeof an identity of a mobile switching center to which the target accesspoint is associated; and information indicative of an identity of a cellto which the target access point is associated; a memory moduleconfigured to store the handoff information; and a processor moduleconfigured to process the handoff information and control a transmittermodule to transmit the handoff information to initiate handoff to thetarget access point.
 12. The apparatus of claim 11, wherein the handoffinformation is transmitted within a handoff supplementary informationnotification message (“HSINM”).
 13. The apparatus of claim 11, whereinthe handoff information is transmitted within a pilot signal measurementmessage.
 14. The apparatus of claim 11, wherein the processor module isfurther configured to perform handoff to the target access point. 15.The apparatus of claim 11, wherein the target access point is a femtoaccess point.
 16. An apparatus comprising: means for receivingtransmitted handoff information from a target access point, the handoffinformation comprising: information indicative of an identity of amobile switching center to which the target access point is associated;and information indicative of an identity of a cell to which the targetaccess point is associated; means for storing the handoff information;means for transmitting the handoff information; and means for processingthe handoff information and controlling the means for transmitting totransmit the handoff information to initiate handoff to the targetaccess point.
 17. The apparatus of claim 16, wherein the handoffinformation is transmitted within a handoff supplementary informationnotification message (“HSINM”).
 18. The apparatus of claim 16, whereinthe handoff information is transmitted within a pilot signal measurementmessage.
 19. The apparatus of claim 16, further means for performinghandoff to the target access point.
 20. The apparatus of claim 16,wherein the target access point is a femto access point.